whoop_recovery

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

With no annotations, the description must disclose behavioral traits. It only lists return data and does not mention that the tool is read-only, any authentication requirements, rate limits, or data freshness. The lack of behavioral context is a significant gap.

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, short sentence that front-loads the key metrics. It is concise but omits important details like parameter usage and behavioral notes. Every word earns its place, but the brevity comes at the cost of completeness.

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 has an output schema (not shown), the description does not need to explain return structure. However, it does not specify the time range precisely (e.g., 'last few days' is vague) or any prerequisites. For a simple data retrieval tool, it is adequate but not thorough.

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 only parameter (days, default 7) has no schema description (0% coverage). The description mentions 'der letzten Tage' (recent days) but does not explain that the 'days' parameter controls how many days back to fetch. It adds minimal value beyond the schema.

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 lists the specific metrics (Recovery Score, HRV, resting pulse, SpO2, skin temperature) and implies a retrieval operation for recent days. It distinguishes itself from siblings like whoop_sleep (sleep data) and whoop_workouts (workout data). However, it lacks an explicit verb like 'get' or 'retrieve', which slightly reduces clarity.

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 guidance is provided on when to use this tool versus its siblings (e.g., whoop_summary, whoop_sleep). The description does not mention use cases, prerequisites, or exclusions, leaving the agent to infer context.

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