Oura Daily Recovery Summary

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior. The description adds value by stating 'non-medical' (important disclaimer) and 'when available' (indicates data availability may vary). This context beyond annotations justifies a score above 3.

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 front-load the purpose and key constraints ('read-only, non-medical'). No redundant phrases; every word contributes to understanding. Ideal conciseness for a tool description.

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?

While the description covers data sources and safety, it misses explaining the time range (days parameter defaults to 7, but tool is called 'daily summary') and does not mention output format options (schema covers that). With an output schema present, return values are documented elsewhere, but the time range ambiguity reduces completeness.

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 67% (2 of 3 parameters have descriptions in the schema itself), so the baseline is 3. The tool description does not add any parameter-specific meaning beyond the schema's built-in descriptions, so it neither improves nor harms parameter clarity.

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 builds a 'practical daily summary' and lists the specific data sources (readiness, sleep, activity, heart-rate, SpO2) when available. This is a specific verb+resource that distinguishes it from sibling tools like individual listing tools or the weekly summary.

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 a consolidated daily overview but does not explicitly state when to use this tool versus alternatives like oura_weekly_summary or individual data listers. No when-not-to or prerequisite guidance is given, though the context of 'daily summary' provides some direction.

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