list_whoop_sleep

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is covered. The description adds genuinely useful context — that results include naps, per-stage durations in milliseconds, and respiratory rate — but omits pagination behavior (how next_token/limit interact) and any note about maximum page size or truncation.

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 compact sentence with no filler, and the resource is front-loaded. It is slightly dense and elliptical ('Page sleep and naps, stage durations...') rather than well-structured prose, but nothing is wasted.

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 four parameters at 0% schema coverage, no output schema, and no annotations describing return shape, the description should at minimum cover date formats and the pagination contract. It gives the content of records but leaves the calling contract essentially undocumented.

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 0%, so all four parameters (start, end, limit, next_token) are undocumented in structured fields and the description must compensate. The word 'Page' hints at pagination but never explains expected formats for start/end dates, the default or maximum for limit, or how next_token continues a result set — a significant gap at this coverage level.

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 uses the vague verb 'Page' but does identify the resource (sleep and naps) and some returned fields (stage durations in milliseconds, respiratory rate). It never distinguishes this listing tool from the close siblings get_whoop_sleep (single record) or list_whoop_cycles, so an agent must infer the list-vs-get distinction from the name alone.

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 use this tool versus get_whoop_sleep or the other list_* tools, and no mention of prerequisites, date-range scoping, or pagination workflow. The agent is left to infer that this is the bulk-retrieval option.

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