oura_daily_summary

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered. The description adds only that it is an 'overview', which is more about scope than behavior, and does not disclose additional side effects, permissions, or rate limits. With annotations covering the safety dimension, a 3 is appropriate.

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 (three sentences plus a parameter list) and front-loaded with the key purpose. The usage guidance follows immediately, then the parameter detail. Every sentence contributes value with no redundancy 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?

Given that an output schema exists and the parameter is well-documented in the description, everything an agent needs to correctly call and interpret the result is present. The description covers what data is returned, when to use it, and the parameter semantics. Complete for a one-call overview 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?

Schema description coverage is 0%, but the description fully compensates by specifying the format ('YYYY-MM-DD') and default ('defaults to today') for the date parameter. This adds meaning well beyond the bare schema type and default null, making the parameter usage clear.

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 a specific verb ('Get') and resource ('a one-call overview') and enumerates the data it returns (sleep score, raw sleep periods, readiness score, daily activity). It also explicitly distinguishes itself from more specific sibling tools by framing itself as an overview, making its purpose 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?

Provides explicit usage guidance: 'Use the more specific tools for fields not covered here.' This tells the agent when to use this tool versus alternatives, which is exactly the kind of routing information needed. No exclusions or caveats are missing.

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