Get WHOOP Body Measurements

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

Beyond the readOnlyHint and idempotentHint annotations, the description adds the required OAuth scope and a medical disclaimer, which are useful behavioral context. It also implicitly confirms it's a read operation consistent with annotations. No contradictions.

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 crisp sentences: purpose, scope, and disclaimer. Zero waste, front-loaded with the descriptive verb and resource.

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 simple read-only resource, the description covers purpose and scope, while annotations cover safety, and the schema covers parameters and output. The output schema exists, so return values are defined elsewhere. Minor gaps like whether measurements are historical or current are negligible for this tool.

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 description itself adds no parameter semantics, but the input schema provides descriptions for two of three parameters (privacy_mode and explicit_user_intent) and an enum/default for response_format, giving roughly 67% coverage. The description could have noted the default response format or privacy behavior, but the schema largely compensates, so a baseline 3 is appropriate.

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 clearly states the verb 'Get' and the resource 'WHOOP body measurements' with specific fields (height, weight, max heart rate), distinguishing it from sibling tools that list cycles, sleeps, etc. It also mentions the authentication scope, reinforcing its specific purpose.

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 description provides clear context for when to use this tool: when needing the authenticated user's body measurements. It doesn't explicitly name alternatives or exclusions, but the resource specificity is sufficient for a simple read tool, so it earns a 4 rather than a 5.

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