get_sleep_daily

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

Annotations cover only readOnlyHint and openWorldHint, so the description's disclosure of the 28-day-per-request cap, automatic chunking, de-duplication by calendarDate, and sorted output is genuinely useful behavioural context an agent would otherwise discover only by failing. It stops short of describing return shape or rate limits.

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?

A single sentence with no filler, and the most important constraint (the 28-day cap) is front-loaded. The bold/backtick markdown is slightly noisy but not wasteful.

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 and no annotations describing the response, the description should explain what a sleep-daily record contains and what the range returns, but it never does. It answers 'how' (chunking) while leaving 'what' entirely unanswered.

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 100% (both start and end are documented as YYYY-MM-DD UTC dates), so the schema carries parameter meaning. The description adds only the implicit range limit, which is a behavioural rather than a semantic detail — baseline 3 applies.

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 never states what the tool does — no verb and no resource. It only describes a chunking constraint on 'Garmin's endpoint', leaving the agent to infer from the name that it returns daily sleep data. Sibling get_sleep_data is not distinguished from it at all.

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 guidance on when to call this versus the closely related get_sleep_data (or get_sleep_data's range variant). The 28-day limit hints at range-splitting behaviour but does not tell the agent which tool to pick for which need.

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