Sleep

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds valuable domain behavior beyond annotations, especially that a night is filed under the wake-up date and that range mode returns nightly summaries rather than detailed series.

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 compact sentences with no filler. The primary single-night behavior is front-loaded, the range mode follows, and the wake-up-date caveat is appended efficiently.

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 the rich annotations, fully described schema, and absence of an output schema, the description supplies everything an agent needs: what data is returned, how range mode is triggered, and the key date-filing convention.

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%, giving a baseline of 3. The description adds behavioral meaning to end_date by explaining that it enables a per-day summary across a range, and it clarifies the date-attribution rule for sleep nights; include_series behavior is left to the schema.

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 states a specific resource (sleep) and distinguishes two modes: one night of detailed sleep data versus a nightly summary over a date range. It names the returned data categories (stages, score, overnight heart rate, respiration), so an agent can identify the tool immediately among health-metric siblings.

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?

It clearly explains that supplying an end_date switches from a single night to a per-day range summary, which is useful selection guidance. It does not explicitly say when to prefer get_daily_overview or get_daily_summaries, so it lacks full alternative routing.

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