List sleeps

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

Annotations already declare the read-only, idempotent, non-destructive profile, and the description adds real context beyond them: the exact metrics returned (performance, efficiency, stage breakdown, disturbances, respiratory rate, sleep need) and the sort order. It still omits pagination/truncation behavior, which matters for a list tool with a limit and next_token.

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 front-loaded sentence naming the resource first, then what it returns, with zero filler or hedging. The metric enumeration is dense but each item is substantive, so nothing meaningful could be cut without losing information.

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 usefully compensates by listing the returned fields, and the default-inclusion of naps is implied by mentioning both sleeps and naps. What is missing is any statement about paging or result-size behavior for a 7-parameter, optional-everything list endpoint.

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%, so dates, days, limit, raw, next_token and include_naps are all documented in the schema itself. The description adds no parameter-level detail (e.g. how 'raw' affects the field list it enumerates), so the 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 names the resource ('sleeps and naps') and enumerates the specific metrics returned, which cleanly separates it from siblings like list_recoveries and list_cycles. It does not explicitly name those siblings or state a list-verb, so an agent still infers 'list all sleeps in a window' rather than being told directly.

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 when-to-use guidance, no mention of when to prefer get_sleep for a single record, and no guidance on paging through large result sets. The only usage-adjacent signal is the ordering note ('most recent first'), which is behavioral rather than a usage rule.

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