get_sleep

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

No annotations are provided, so the description carries the behavioral burden. It makes the read-only nature apparent via 'Get' and clarifies what data is included. However, it does not disclose defaults (e.g., limit default of 1), date-range semantics, or how naps are handled—details left to the schema.

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?

The description is a single, front-loaded sentence with no filler. It starts with the action and resource, then lists the relevant data categories, making it easy for an agent to parse quickly.

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?

For a simple getter with four optional parameters, the description is mostly complete: the schema covers the parameters and the description covers the return domains. Since there is no output schema or annotations, a bit more detail about response shape or default behavior would help, but the core calling context is sufficiently clear.

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 the baseline is 3. The description does not add meaning beyond the schema for parameters like limit, start_date, end_date, or include_naps; it only describes the output data categories rather than the parameters themselves.

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 a specific verb ('Get'), identifies the resource ('WHOOP sleep data'), and enumerates the returned domains (duration, efficiency, sleep stage breakdown, disturbances, respiratory rate). It is clear and informative, though it does not explicitly distinguish itself from sibling tools like get_recovery or get_body_measurements.

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 tool name and description: an agent can infer to use this when sleep data is needed. However, there is no explicit guidance about when to prefer this over sibling tools such as get_recovery, nor any mention of filters or prerequisites beyond what the schema provides.

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