query_body_measurements

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states 'Query body measurements' and gives no information about return formats, data granularity, side effects, read-only status, or any other behavioral aspects. The description is essentially non-informative beyond the tool name.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

At four words, the description is under-specified rather than appropriately concise. It lacks even the basic structure needed to convey a clear meaning, sacrificing all substantive content for brevity. The description does not earn its place because it provides zero informational value beyond the tool name.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has four parameters, no output schema, and no annotations, the description is completely inadequate. It does not explain what body measurements are included, how date ranges work, what metrics are available, or what 'latest_only' means. An agent would be left guessing about the tool's full behavior and required inputs.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has four parameters (metrics, end_date, start_date, latest_only) with zero descriptions. The description adds no meaning to any of these parameters, failing to compensate for the 0% schema description coverage. It does not explain date format, allowed metric values, or the effect of latest_only, leaving all parameter semantics unexplained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Query body measurements' is a tautology, restating the tool name verbatim without adding any new information about what the tool does, what kind of body measurements it retrieves, or how it differs from sibling tools like query_metric_series or query_heart_rate. It names a verb and resource but provides no distinct purpose clarification.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this tool versus alternatives. No mention of prerequisites, typical use cases, or exclusions. The sibling tools include multiple measurement queries, and this description does nothing to differentiate them, leaving the agent without direction for tool selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.