List cycles

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

Discloses default date range (last 7 days) and pagination behavior (limit capped at 25, next_token cursor), which go beyond the readOnlyHint annotation. It also clarifies the semantics of a cycle, adding useful context about the data model.

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?

Starts with a clear one-line summary, then a brief context sentence defining cycles, followed by a succinct Args list. No wasted words; each 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?

The description covers the essential operational aspects: default behavior, pagination, and the central concept of cycles. With an output schema present, return values are already specified, so the description need not enumerate 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 descriptions are absent (0% coverage), but the Args section explains each parameter's meaning, format (ISO 8601), default behavior, and pagination use. This fully compensates for the schema gap.

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 lists physiological cycles with specific metrics (strain, heart rate, kilojoules) and defines cycles as WHOOP's day bounded by sleep. This distinguishes it from sibling list tools for sleeps, workouts, and recoveries.

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?

Explains what a cycle is and its role as the key join key, implying when cycle-level data is needed. It does not explicitly name alternative tools or contrast with them, but the context is clear enough for an agent to select it appropriately.

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