Get WHOOP recovery history

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false, covering safety and side-effect transparency. The description adds no behavioral detail beyond listing fields, but this is acceptable given existing annotations. It doesn't contradict 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?

The description is a single sentence listing fields, which is concise but not structured (e.g., no verb, no indication of what constitutes 'recent'). It lacks front-loading of key purpose. Could be improved with a clear action statement.

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?

With an output schema present, the description does not need to detail return values. However, it mentions 'recent recovery score' singularly, which may confuse about whether one score or a list is returned. The parameter 'days' implies multiple, but it's not explicit. Overall adequate for low complexity 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 single parameter 'days' is fully described in the schema (min, max, default, description). The tool description does not add any additional semantic meaning beyond the schema, so baseline score of 3 applies (schema coverage is 100%).

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 title includes 'Get' and the description lists the specific recovery metrics returned (recovery score, HRV, etc.), clearly indicating the tool fetches recovery history. It distinguishes from siblings like whoop_workout_history and whoop_sleep_history by focusing on recovery data.

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?

No explicit guidance on when to use this tool over alternatives (e.g., when to use whoop_latest_overview vs this). No mention of prerequisites or constraints. The description simply states what data is returned without contextual usage advice.

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