WHOOP Data Inventory

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. The description adds valuable context by stating it does not call WHOOP APIs and does not expose user data, which clarifies the tool's non-invasive nature and privacy boundary beyond the annotation flags.

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 two sentences, immediately states the purpose, and then adds a key limitation. There is no filler or redundant wording; every word earns its place.

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's simple inventory purpose and the presence of an output schema, the description adequately covers the tool's role, limitations, and content. It could optionally explain the response_format parameter, but the overall completeness is sufficient for orientation.

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 description does not mention the response_format parameter at all. Since schema description coverage is 0%, the description should compensate, but it remains silent on how the parameter affects the output. The schema's enum and default provide some self-evidence, but the description adds no semantic value for this parameter.

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 uses the specific verb 'inventory' and lists concrete content areas (data domains, auth scopes, privacy boundary, recommended first calls). It explicitly distinguishes itself by stating it does not call WHOOP APIs or expose user data, making its role clear relative to sibling data-fetching tools.

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 phrase 'recommended first calls' implies this is an entry-point tool for orientation, and the note about not calling WHOOP APIs suggests using it when you need an overview rather than actual data. However, it does not explicitly name alternative tools or provide direct when-to-use versus when-not-to-use guidance.

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