WHOOP Data Inventory

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

Description explicitly states it does not call WHOOP APIs or expose user data, which aligns with annotations (readOnlyHint, idempotentHint, non-destructive). Provides additional behavioral clarity beyond 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 concise sentences, front-loaded with key information, no wasted words.

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 presence of an output schema (not shown but noted), the description sufficiently explains what the tool inventories. No missing information for its informational purpose.

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 only parameter (response_format) is self-explanatory from the schema's enum, but the description does not mention it or its possible values. With 0% schema coverage, some param guidance would be beneficial, though the parameter is trivial.

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 tool inventories WHOOP data domains, auth scope requirements, privacy boundaries, and recommends first calls. It explicitly says it does not call APIs or expose user data, distinguishing it from sibling tools that perform actual data retrieval.

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 implies use for informational purposes before making API calls, but does not explicitly state when to use it over siblings. However, the purpose is clear enough for an agent to choose it for initial exploration.

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