Get Body Measurements

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds the returned field names and authentication context, but no additional behavioral traits like rate limits or pagination. This is adequate but not rich, consistent with the reduced burden when annotations are present.

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 short, front-loaded with the core action, and structured with a bulleted list for return fields. The final sentence on use cases earns its place. No redundant or extraneous content.

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?

For a zero-parameter, read-only tool with strong annotations, the description fully covers what is needed: the resource retrieved, the exact return fields, and practical applications. There is no output schema, so the description appropriately explains the return values. No gaps.

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 tool has zero parameters and an empty input schema, so there are no parameter details to document. The baseline for no parameters is 4, and the description correctly omits any irrelevant parameter information.

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 opens with a specific verb+resource: 'Retrieves body measurements for the authenticated Whoop user.' It clearly differentiates from sibling tools by naming the resource (body measurements) and listing the exact fields returned, which are distinct from profile, recovery, sleep, workouts, cycles, and health overview.

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?

The phrase 'Useful for calculating calories burned and personalizing workout recommendations' conveys clear intended use cases. However, it does not explicitly mention when not to use this tool or point to alternative sibling tools, so it stops short of a 5.

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