Daily overview

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the description does not need to restate safety. It adds meaningful behavioral context beyond annotations: missing permissions cause the affected data types to appear under `unavailable` rather than failing the call, and it lists the returned categories for a tool with no output schema.

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 front-loaded with the primary action and scope, then efficiently layers in usage routing, default behavior, and fallback behavior. The long data-type list is information-dense but earns its place by telling the agent exactly what a 'daily overview' returns.

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 no output schema, the description carries the burden of explaining return contents and does so by enumerating the included data categories. It also covers selection guidance, default behavior, and partial-availability handling, leaving no significant gap for an agent deciding to call this 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 coverage is 100%, so the schema already documents the single `date` parameter, including its default. The description adds a small refinement beyond the schema: 'Omit date for the latest day with a sleep or readiness score,' which clarifies what 'latest day' means in practice.

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 opens with a specific verb+resource: 'Get everything Oura recorded for one day in a single call.' It enumerates the data types covered and explicitly distinguishes itself from get_trends (multi-day) and list_* tools (one data type over a range), so an agent can select it confidently against siblings.

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?

It gives explicit when-to-use guidance: 'Start here for today, last night or any single date,' and names alternatives for other cases ('use get_trends for multi-day questions and the list_* tools for one data type over a range'). It also clarifies the default when date is omitted, leaving nothing to inference.

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