WHOOP Sleep

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

Annotations already cover read-only, idempotent, and non-destructive behavior. The description adds the 'Requires read:sleep scope' authorization detail, which is a meaningful behavioral constraint beyond the structured annotations. The 'Not medical advice' disclaimer is additional context, though not strictly behavioral.

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 two sentences with front-loaded purpose, a scope requirement, and a disclaimer. Every word earns its place; no redundant content or filler.

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 rich annotations, an output schema, and a well-described input schema, the description sufficiently orients the agent. It could mention privacy_mode behavior, but that is already handled by the schema. The core retrieval purpose and auth requirement are covered.

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%, with id and privacy_mode well-documented, and explicit_user_intent also described. The description itself adds no parameter-specific meaning, so the baseline of 3 applies because the schema carries the load.

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 clearly states the tool 'gets one WHOOP sleep activity by UUID', using a specific verb and resource with a unique identifier. This distinguishes it from sibling list tools (e.g., whoop_list_sleeps) and cycle-specific tools.

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 UUID-based requirement implies you need a specific ID, and the mention of 'read:sleep scope' provides a prerequisite. It does not explicitly name alternatives or exclusions, but the context is clear: use this when you have a UUID and need a single sleep record.

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