Cycle by id

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

The description confirms the read-only behavior (consistent with readOnlyHint annotation) and explains the optional parameters' effects, including the include_raw flag for raw API records. No contradictions with annotations.

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?

Two sentences, front-loaded with the main purpose, no unnecessary words. Every sentence adds value.

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 4 parameters, an output schema exists, and annotations are provided, the description fully covers the key behavior and optional features. No gaps.

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?

With 0% schema description coverage, the description compensates by explaining three parameters: include_recovery, include_sleep, and include_raw. It adds context beyond the schema titles, though cycle_id is not explicitly described (but is clear from context).

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 verb 'get', the resource 'one cycle by id', and the optional inclusions of recovery and sleep. This distinguishes it from sibling tools like 'get_cycles' (plural) and others that fetch different data.

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 explains when to include recovery, sleep, and raw data, providing context on WHOOP's data relationships. However, it does not explicitly state when to use this tool vs. alternatives like 'get_cycles', though the singular nature implies it.

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