WHOOP Sleeps

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

Annotations already declare read-only, idempotent, and non-destructive behavior. The description adds valuable context beyond that: requires read:sleep scope, returns scored sleep metrics, supports pagination, and includes a 'not medical advice' disclaimer.

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 three concise sentences: the first states purpose, the second adds return details and features, the third covers auth scope and disclaimer. No fluff or redundancy.

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 tool has 9 parameters and an output schema, the description provides enough high-level context for selection and invocation: what it lists, key features, auth requirement, and non-medical nature. Output schema handles return values, so not needing to describe them.

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 high (89%), with detailed descriptions for parameters like date format and max page size. The description's mention of 'start/end filters' and 'pagination' adds little beyond the schema, so it meets the baseline but does not elevate.

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 it 'List WHOOP sleep activities' with a specific verb and resource. It distinguishes from sibling tools by focusing on sleep and mentioning returned metrics (stages, performance, consistency, efficiency).

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 description provides clear context for when to use the tool: listing sleep activities with start/end filters and pagination. It does not explicitly mention alternatives like whoop_get_sleep, but the context implies this is for multi-sleep queries, which is sufficient for a 4.

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