query_body_measurements

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

With no annotations, the description carries the full burden of disclosing behavior. It merely says 'Query' implying a read operation, but it does not disclose required date parameters, the meaning of 'latest_only', or what the returned data looks like. No behavioral traits beyond the literal query are revealed.

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?

The description is extremely concise at three words, but it is under-specification rather than useful conciseness. It provides no structure or key information, making it less helpful than a longer description with relevant details.

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's complexity (4 parameters, required start/end dates, optional metrics, and no output schema), the description is drastically incomplete. It fails to convey parameter semantics, usage context, or return behavior, leaving the agent without sufficient information to use the tool correctly.

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 input schema has 4 parameters with no descriptions, and the tool description provides zero explanation of any parameter. Since schema description coverage is 0%, the description was expected to compensate, but it does not – parameters like 'metrics', 'latest_only', and proper date formats are left 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 states a verb ('Query') and a resource ('body measurements'), but it is vague and does not specify the scope, time range, or how it differs from sibling tools like query_metric_series or query_heart_rate. It is not a tautology, but it lacks enough specificity to be fully clear.

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?

No guidance is provided on when to use this tool versus other query tools. There is no mention of alternatives, prerequisites, or context. The agent is left without any direction.

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