WHOOP Wellness Context

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

Annotations already declare the tool as read-only, idempotent, and non-destructive. The description adds that the tool normalizes data into a shared shape, but does not elaborate on the shape or any behavioral nuances. It does not contradict annotations, but adds minimal value beyond what annotations provide.

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 a single sentence that concisely conveys the core purpose. Every word contributes meaning, with no redundancy or filler.

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?

The tool has an output schema, so the return format is presumably covered. However, the description omits prerequisites (e.g., need for prior authentication or data fetching) and does not guide the agent on when to invoke this tool versus siblings. Given the complexity of 6 parameters, more contextual guidance would be beneficial.

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 description coverage is only 33% (days and timezone have descriptions). The tool description does not mention any parameters or their purposes, leaving the agent to infer meaning from parameter names alone. Since coverage is low, the description should compensate but does not, resulting in a below-adequate score.

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 uses a specific verb 'normalize' and clearly states the resource (WHOOP data into shared wellness_context shape). It differentiates from siblings by mentioning the target use case (exercise recommendation engines and Telegram agents), making the tool's purpose distinct among many WHOOP tools.

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 implies usage for creating a unified wellness context but does not explicitly state when to use this tool versus alternatives like whoop_daily_summary or whoop_recovery_trend. No exclusions or prerequisites are provided, leaving the agent with only implicit context.

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