Sleep details per night

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

Annotations already declare readOnlyHint=true, and the description adds behavioral details: default date range (last 7 days), inclusion of bedtime recommendations when available, and specifics on heart rate and HRV. No contradiction with annotations.

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: first enumerates returned data types, second provides usage examples and defaults. No filler; every sentence adds value. Front-loaded with key content.

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 3 optional parameters, no output schema, and read-only annotation, the description sufficiently covers expected output (sleep stages, heart rate, etc.), default behavior, and typical queries. It is complete for this tool's complexity.

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 baseline is 3. The description mentions date range defaults but does not add new semantic info beyond what the schema descriptions provide (e.g., no mention of response_format). Thus, it meets but does not exceed baseline.

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 'Per-night sleep sessions' with specific metrics (bed/wake times, sleep stages, heart rate, etc.), which distinguishes it from sibling tools like 'oura_get_sleep' (likely a summary). It also provides example queries like 'when did I fall asleep', grounding its purpose.

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 lists use cases ('Use for "when did I fall asleep"...') and mentions the default scope (last 7 days). However, it does not exclude scenarios where sibling tools should be used instead, such as when only aggregate sleep scores are needed.

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