whoop_sleep

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

No annotations are provided, so the description carries the full burden. It merely lists metrics without disclosing behavioral traits such as data granularity, time range, or response format. With an output schema present, the description fails to clarify what the tool returns or any side effects.

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 concise (a single line), but it lacks structure. It reads as a list rather than a coherent sentence. While not verbose, it could be improved by adding a verb and parameter context.

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 existence of an output schema and multiple sibling tools, the description is incomplete. It does not explain what the output contains or how to distinguish from related tools. The single parameter and list of metrics are insufficient for context.

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?

The input schema has one parameter 'days' with 0% description coverage. The description does not mention this parameter, its purpose, or how it affects results. The description adds no value beyond the schema itself.

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 lists sleep-related metrics (duration, phases, performance, consistency, respiratory rate) but lacks an explicit verb stating what the tool does (e.g., retrieves, gets). This makes it somewhat vague, though the list implies the tool provides sleep data. The purpose is clearer than a tautology but not specific enough to distinguish from siblings like whoop_summary.

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?

No guidance is provided on when to use this tool versus alternatives such as whoop_recovery, whoop_summary, or whoop_cycles. There is no mention of context, prerequisites, or exclusions.

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