whoop-get-recovery-for-cycle

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

No annotations provided, so description must fully disclose behavior. It does not state that this is a read-only operation, whether authentication is required, or any side effects. The description is minimal and fails to add behavioral context.

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 extremely concise at one sentence with no fluff. However, it could be slightly improved by adding a brief note about prerequisites or output without sacrificing brevity.

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?

For a simple retrieval tool with one parameter, the description is minimally adequate. It could mention that the cycleId must be obtained from 'whoop-get-cycle-collection' or 'whoop-get-cycle-by-id', and that the recovery data typically includes metrics like score, heart rate variability, etc., especially since there is no output schema.

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 coverage is 100% with 'cycleId' described in the schema. The description adds no additional meaning beyond the schema, such as explaining how to obtain a valid cycleId or the expected format. Baseline 3 is appropriate when schema is complete.

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 'recovery data', and the scope 'for a specific cycle'. It distinguishes this tool from siblings like 'whoop-get-recovery-collection' (returns all recovery) and 'whoop-get-cycle-by-id' (returns cycle metadata).

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?

No guidance is provided on when to use this tool versus alternatives. For example, it does not mention that to retrieve recovery for multiple cycles, one should use 'whoop-get-recovery-collection' with cycle filters.

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