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 states the tool is read-only, throws SuuntoNotFoundError for missing data, and requires a subscription (404 otherwise). This adds important behavioral context beyond the schema, though it lacks details on rate limits or data freshness beyond what the schema provides.

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 concise at 5 sentences, each serving a distinct purpose: return value, error condition, alternative tool, prerequisite, and read-only nature. No unnecessary words, and it is front-loaded with the key result.

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 simple single-parameter tool with no output schema, the description covers: what is returned (fields and units), error handling, alternative for ranges, subscription requirement, and idempotence. It is sufficiently complete for an agent to use correctly.

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 covers 100% of parameter description, including format, constraints, and guidance on usage (e.g., use yesterday's date). The tool description does not add additional semantic meaning beyond what is already in the schema. Baseline score of 3 is appropriate.

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 tool returns recovery and HRV summary for a single date, listing specific fields. It distinguishes from sibling 'list_recovery' which covers a date range. The purpose is specific and unambiguous.

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 explicitly says when to use (one date) and when to use the alternative 'list_recovery' (date range). It also mentions the prerequisite of a Recovery API subscription and the resulting 404 error, guiding the agent on proper usage.

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