Export all WHOOP data

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

Explicitly states no data is uploaded, describes output files and their contents, and warns about processing time. Annotations are consistent; adds safety and scope details beyond structured fields.

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?

Extremely concise with no filler. Front-loaded with action and outputs, then safety, then parameter details. Every sentence adds value.

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 three parameters, existing output schema (implied by description), and sibling context, the description covers all needed information for an agent to invoke correctly.

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?

With 0% schema description coverage, the description fully explains each parameter: date formats for start/end and purpose of include_raw. This compensates entirely for schema's lack of documentation.

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 specifies the exact action (export), the resource (WHOOP records in date range), and the output (three local files). It clearly distinguishes from sibling getter tools that fetch single items or summaries.

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?

Provides clear context for date parameters and performance warning for large ranges. While it doesn't explicitly state when not to use, the description implies this is for bulk exports, contrasting with sibling tools for single queries.

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