Get sleep summaries (date range)

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, so the safety profile is covered. The description adds genuinely useful behavior: the field-level contents of each record, the units (seconds), and the hard 31-day request ceiling — the latter partially duplicating the schema's endDate note.

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?

Purpose is front-loaded in the first clause, the field list is dense but scannable, and the closing constraint sentence is short. No filler or restated title.

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, enumerating returned fields and units is exactly the right compensation, and annotations cover safety. Minor gaps remain: behavior for nights with no recorded sleep, and whether the 31-day limit is enforced as an error or truncation.

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% and both parameters are well documented with format, inclusivity, and the 31-day limit. The description adds no parameter-level meaning beyond repeating the range cap; 'durations are in seconds' concerns return values, not inputs.

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 with scope: 'one sleep summary per night for a date range', and enumerates the returned fields. It implicitly differentiates from the single-night sibling garmin_get_sleep via 'per night for a date range', but never names that sibling explicitly.

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?

Usage is implied by the range framing and the 31-day cap, so an agent can infer this is the batch version. However, it never says when to prefer this over garmin_get_sleep or how to handle ranges longer than 31 days (split vs. error).

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