Get sleep summaries

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 genuinely new behavior: the default window is the 7 days ending today and long ranges are silently fetched in 31-day chunks. It doesn't mention rate limits or result ordering, but the added paging behavior is the kind of detail an agent otherwise couldn't know.

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: purpose first, parameter semantics second. Every clause carries information — defaults, format, inclusivity, and the paging rule — with no 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?

For a 2-optional-param read tool with no output schema, the description covers defaults and range handling adequately; return shape is deferred to garmin_get_sleep ('same fields'), which assumes the agent knows that sibling. A one-line note on what each record contains would close the remaining gap.

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 0% and the bare 'string'/null params carry no meaning, so the description does the full job: format YYYY-MM-DD, inclusivity, default of the trailing 7 days, and that any range length is acceptable. Nothing needed to call the tool is left to guesswork.

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+resource: nightly sleep records across a date range, and explicitly relates itself to the sibling garmin_get_sleep by noting identical fields. The plural/range framing plus 'Use it for sleep trends' makes the distinction from the single-night sibling apparent without opening either schema.

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?

'Use it for sleep trends' gives clear positive guidance on when to reach for this tool over the single-night getter. It stops short of an explicit when-not statement (e.g. 'for a single night use garmin_get_sleep'), leaving that to inference from the sibling reference.

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