whoop-get-recovery-collection

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

With no annotations, the description should disclose behavioral traits. It only mentions pagination but omits authorization requirements, rate limits, data availability conditions, or whether the tool returns errors for empty results. The description is too sparse for a data retrieval tool.

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 with no unnecessary words. It conveys the essential purpose and pagination feature without fluff.

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 complexity of four parameters, no output schema, and no annotations, the description is insufficient. It does not explain the return format, pagination behavior (e.g., how to use nextToken), or handle edge cases. The agent lacks information to fully understand the tool's behavior.

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?

All four parameters have descriptions in the schema (100% coverage), so the baseline is 3. The description adds only the word 'paginated', which hints at nextToken usage but does not enrich parameter meaning beyond the schema. No new semantics are provided.

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 action (get), resource (recovery data), scope (for a user), and feature (paginated). It distinguishes from sibling tools like 'whoop-get-recovery-for-cycle' which targets a specific cycle, and 'whoop-get-cycle-collection' which retrieves cycles, not recovery 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?

No guidance is provided on when to use this tool versus alternatives (e.g., 'whoop-get-recovery-for-cycle' for a specific cycle). There are no instructions on prerequisites, sequence, or exclusion criteria.

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