Daily summary

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

The description adds context by listing the data components returned, but readOnlyHint already indicates no destructive behavior. The description does not cover other behavioral aspects like auth requirements or rate limits, so score 3 is appropriate.

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 three sentences, front-loaded with the core purpose and key information. Every sentence adds value without redundancy.

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, the description sufficiently covers the tool's inputs and outputs. It explains the parameter format and lists the data types returned. For a single-parameter tool, it is complete.

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 compensates well by detailing the day parameter's accepted formats: 'today | yesterday | N days ago | YYYY-MM-DD'. However, it could be more exhaustive (e.g., range or relative days).

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 retrieves one day of WHOOP data with specific components (recovery, sleep, strain, workouts, summary). It also distinguishes itself as the best first tool for common queries, setting it apart from sibling 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 description explicitly recommends this tool for 'how am I doing' or 'how did I sleep' questions, providing clear guidance on when to use it. It also explains the day parameter format. However, it does not explicitly mention when not to use this tool.

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