Get sleep

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds real value beyond that: what the response contains (scores, stage seconds, HR, SpO2, respiration, naps, feedback) and the precise meaning of the date window ('night ending on date', 'the morning you woke up').

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 short blocks: return payload first, then the parameter definition. No filler sentences, and the most decision-relevant clause (which night) is front-loaded.

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?

With no output schema, the description correctly enumerates what comes back, and it fully specifies the single parameter. It stops short of covering edge behavior such as what is returned when no sleep was recorded, which would matter for a health-data 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%, so the description must carry the parameter. It does: format (YYYY-MM-DD), the semantic anchor (the morning you woke up, not the evening), and the default (today = last night). That is exactly the disambiguation an agent needs.

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?

States a specific verb and resource: 'The full sleep record for the night ending on date,' and enumerates the contents. The word 'full' implicitly contrasts with garmin_get_sleep_summaries, but no sibling is named explicitly, so the differentiation is left partly to inference.

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?

There is no explicit when-to-use / when-not guidance and no named alternative such as garmin_get_sleep_summaries. Usage is only implied by the 'full record for the night' framing and the date semantics.

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