Get WHOOP Body Measurements

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

Annotations already indicate readOnly, idempotent, not destructive. Description adds the scope requirement and a 'not medical advice' disclaimer, but does not elaborate on rate limits, data freshness, or error scenarios. Adds some value but limited beyond annotations.

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?

Three sentences, no redundancy. Purpose is front-loaded in the first sentence, followed by essential scope requirement and a disclaimer. Every sentence adds necessary information.

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 simple read operation, rich annotations, and output schema presence, the description covers the essential aspects. However, it could mention that data is for the authenticated user only (implied) and note if multiple records can be returned (likely not). Minor gaps prevent a perfect score.

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?

Schema has 50% description coverage: privacy_mode is well-described, but response_format lacks any description in the schema. The tool description itself does not add parameter-level meaning, missing an opportunity to clarify the response_format parameter.

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?

Clearly states verb 'Get', resource 'body measurements', and lists specific measurements (height, weight, max heart rate). Distinguishes from sibling tools that retrieve other data types like profile or cycles.

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?

States the required OAuth scope (read:body_measurement) but does not provide when-to-use or when-not-to-use guidance compared to other get tools. No mention of alternatives or exclusions.

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