WHOOP Data Inventory

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

Annotations cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds a meaningful clarification: no WHOOP API calls and no user data exposure, confirming the tool is static metadata. This reinforces rather than repeats the annotations, though it omits how large or fresh the inventory is.

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 sentence fragments, front-loaded with the resource being inventoried followed by the scope/limitation clause. No filler, though the second clause reads as a fragment rather than a complete statement.

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?

An output schema exists, so return shape need not be described. The description covers purpose, scope, and non-side-effects, which is sufficient for a zero-required-parameter read tool; only the response_format parameter is left undocumented.

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?

There is a single optional parameter (response_format, enum markdown/json, default markdown) with 0% schema description coverage, and the description never mentions output formatting. The parameter is self-explanatory by name and enum, so impact is limited, but the description does not compensate 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?

States a specific verb (inventory) and enumerates the resources it covers: data domains, auth scope requirements, privacy boundary, and recommended first calls. It is clearly distinguishable from data-fetching siblings, though it does not explicitly differentiate itself from adjacent meta-tools like whoop_capabilities or whoop_quickstart.

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 negation 'Does not call WHOOP APIs or expose user data' implies this is a safe orientation/introspection call, which hints at when to use it. However, it never states when to prefer it over whoop_capabilities, whoop_quickstart, or whoop_agent_manifest, so the agent must infer the routing.

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