Get sleep

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is fully covered by structured data. The description adds nothing on top of that—no note on what the compact vs raw response contains or any auth/rate context—so it earns little credit beyond the annotations.

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 six-word sentence with zero waste and the key noun-verb information front-loaded. It is efficient, though arguably terse to the point of under-specification for a tool with two parameters.

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?

Complexity is low and the schema plus annotations carry most of the load, but with no output schema the description could still say what a sleep record contains or how compact versus raw output differs. Given the rich annotations and full schema coverage, a 3 is adequate but not complete.

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 both the UUID sleep_id and the raw flag are fully documented in the schema itself (including that raw returns WHOOP's unprocessed objects). The description adds no parameter meaning beyond that, 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?

"One sleep or nap by id" states the resource (sleep/nap record) and that retrieval is by a single identifier, implying a point-fetch. However, the phrasing is minimal and never explicitly distinguishes this from the sibling list_sleeps, so the agent must infer the singular-vs-list split from the word "One".

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 stated when-to-use guidance, no mention of when to prefer list_sleeps instead, and no prerequisites. The "by id" fragment hints that an identifier is required, but no alternative is named or contrasted.

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