WHOOP Sleep

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

Annotations already declare the full safety profile (readOnly, idempotent, non-destructive), so the bar is lower. The description adds the required read:sleep scope and a 'not medical advice' caveat, which is useful auth/domain context, but says nothing about payload size or how privacy_mode affects what is returned.

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?

Three tight sentences with the purpose front-loaded, followed by the prerequisite and the caveat. No filler; every clause earns its place.

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 annotations covering safety and an output schema covering return structure, the description supplies purpose, scope prerequisite, and a disclaimer, which is nearly enough for a read tool. It is only missing explicit guidance on choosing among the sleep-related siblings.

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 75%, so the schema carries most param documentation (privacy_mode, explicit_user_intent are already described). The description only alludes to the id param ('by UUID') and adds no detail on privacy_mode=raw escalation or response_format; baseline 3 for high coverage.

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?

States a specific verb (Get) and resource (one WHOOP sleep activity by UUID), and the singular framing distinguishes it from the sibling whoop_list_sleeps and the related whoop_get_cycle_sleep. An agent can tell what it returns without opening the schema.

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?

The 'one ... by UUID' framing implicitly signals single-item retrieval versus the list_sleeps sibling, and the scope requirement is a prerequisite. However, it never explicitly says when to choose this over whoop_list_sleeps or the cycle-based sleep variants, so the agent must infer.

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