I'm not saying they need to, but in the past it has seemed like when Apple provided an affordance, they also had a clear use case. If nothing else, you could fully use the device/service in the way they describe, and that would sufficiently justify its adoption for many. With Health, I'm not seeing that. I wonder if this will threaten the overall adoption of Health, which in general seems like not a terrible idea - anything that gets people thinking more about their activity and diet seems like a good thing.
One could argue that their solution is to leave it to third party devices and integration. Apple doesn't need to make a scale to help you track your weight (Withings has already done it, as I'm sure others have), nor does it want to touch the quagmire that is nutrition by claiming to measure the nutritional value of any food. Let some food-related startup do that dirty work, as long as Apple provides some interface for the measurement to end up in this data silo.
This argument seems weaker to me than the argument seemed when Apple first started accepting apps for the iPhone (later iOS). Health currently leaves huge swaths of its UI barren for lack of data, and I'm not sure that hardware developers can swarm to fill in those gaps the way software developers could with the platform.
Maybe I missed the part of their talk where they made it obvious how they envisioned Health (and HealthKit) to be used in a fuller way; if that's the case, I'd appreciate a pointer.