WHOOP Cycle

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the description's main behavioral addition is the required scope ('read:cycles'). This provides useful context beyond the annotations. No contradictions are present.

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 a single sentence that efficiently conveys the purpose and a key requirement (scope). It is front-loaded with the core action and resource, and every word is necessary.

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 an output schema and comprehensive annotations, the description is sufficiently complete for a simple retrieval operation. It could optionally mention the privacy or format options, but the parameter schema handles that. Overall, it provides enough context for correct invocation.

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?

The input schema covers 67% of parameters with descriptions. The description reinforces the 'id' parameter by stating it is numeric, but does not provide additional meaning for `privacy_mode` or `response_format` beyond what is in the schema. The description adds minimal value over the schema.

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 WHOOP cycle', and the method 'by numeric cycle id'. This distinguishes it from `whoop_list_cycles` which lists cycles, and other single-item retrieval tools like `whoop_get_sleep`.

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 includes a scope requirement ('Requires read:cycles scope'), which provides context for when the tool can be used. However, it does not explicitly state when not to use it or mention alternatives, such as using `whoop_list_cycles` to find the specific id.

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