get_recovery

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

No annotations are provided, so the description carries the full burden. It discloses that results are ordered newest first and lists the data fields. However, it does not explicitly state that the tool is read-only or safe, nor does it mention any potential side effects or limitations.

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?

Two sentences with no wasted words. The first sentence delivers the core functionality, the second adds crucial context. Every part earns its place.

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 (expected), the description does not need to detail return values. It sufficiently covers the source, metrics, time range, ordering, and exclusivity. Minor gap: no mention of pagination or result limits, but acceptable for a simple retrieval 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 input schema has one parameter 'days' with 0% schema description coverage. The description adds meaning by specifying that it retrieves data 'from the last `days` days', clarifying the semantics beyond the schema's type and default.

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 'Returns' and the resource 'WHOOP recovery records', listing specific metrics. It also distinguishes from siblings by noting 'WHOOP-only', differentiating from Apple Health and implying no equivalent in other 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 retrieving recent recovery data ('from the last `days` days, newest first') and specifies WHOOP-only, hinting at when not to use (Apple Health users). However, it does not explicitly mention when to use this tool versus its siblings.

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