WHOOP Recoveries

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

Annotations already indicate readOnlyHint, openWorldHint, idempotentHint, and destructiveHint. The description adds behavioral details beyond these: the default sort order (by sleep start time descending), the specific fields returned (and conditionally 'when scored'), and the scope requirement. This adds meaningful context for safe and effective use.

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 three sentences, each serving a distinct purpose: (1) action and sort, (2) return fields, (3) scope and disclaimer. There is no redundancy, it is front-loaded with core purpose, and every word contributes to understanding. Ideal conciseness.

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 (8 parameters, 0 required, output schema present), the description covers the essential behavior, returned fields, and scope. It does not explain pagination (all_pages, max_pages, next_token) or the privacy_mode parameter, but these are in the schema. The description is complete enough for typical usage scenarios.

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 high (88%), so the input schema already documents most parameters. The description does not add new parameter-level details; however, it sets context with the sort order, which is not a parameter but an implied behavior. No contradiction or enhancement beyond the schema, hence baseline 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 clearly states the action ('List'), the resource ('WHOOP recoveries'), the sort order ('sorted by related sleep start time descending'), and specifies the returned metrics ('recovery score, HRV, RHR, SpO2 and skin temperature when scored'). It also includes the required scope and a disclaimer, making the purpose precise and distinguishing it from sibling tools like whoop_list_sleeps or whoop_list_workouts.

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 mentions the required scope ('read:recovery') and a disclaimer ('Not medical advice'), but it does not provide guidance on when to use this tool versus alternatives such as whoop_get_recovery, whoop_recovery_trend, or whoop_get_cycle_recovery. No explicit when-not or comparative advice is given, resulting in average usage guidance.

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