get_recovery

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

No annotations are provided, so the description must carry the full burden. It states what data is returned but does not disclose read-only behavior, timezone handling, authentication requirements, rate limits, or error behavior. The default-date behavior is mentioned, but other behavioral context is lacking.

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 extremely concise, front-loaded with the core purpose, and the args section is clean and readable. Every sentence earns its place with no repetition or filler.

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?

The tool is simple with one optional parameter, and the description covers the essential input, but with no output schema the return structure of sleep, stats, and readiness is left undefined. Some caveats like timezone or data availability are missing, making this minimally adequate.

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 0% and the only parameter, date, is fully explained in the description with format (YYYY-MM-DD) and default semantics ('Defaults to today'). This adds significant meaning beyond the schema's bare default null.

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 identifies the tool as retrieving sleep, daily stats, and training readiness for a specific day, with a default of today. This is a specific verb+resource+scope combination that distinguishes it from siblings like get_trends or get_activity.

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 gives parameter usage (date format and default) but provides no guidance on when to use this tool versus alternatives such as get_trends or garmin_status. No when-not-to-use or alternative recommendations are offered.

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