get_recovery

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

No annotations exist; description fully discloses: read-only, empty payload for no data, subscription dependency with 404 error, date constraints for reliable results.

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?

Six sentences, each adding value. Front-loaded with primary action, followed by key details. No fluff or redundancy.

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 single required parameter, no output schema, and no annotations, description covers all needed context: return structure, edge cases (empty payload, errors), and setup requirements.

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 coverage is 100%, but description adds critical context about sync frequency, reliable date range, and expected error for today/future dates, going beyond schema examples.

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?

Clearly states verb ('returns'), resource ('recovery and HRV time-series samples'), and scope ('for one calendar day'). Distinguishes from sibling 'list_recovery' by specifying single-day vs date-range.

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?

Explicitly provides alternative tool ('Use list_recovery for a date range'), prerequisites ('Requires Recovery API subscription'), error conditions ('returns 404 without it'), and date-validity guidance ('use yesterday or earlier').

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