get_today_summary

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

Discloses the returned data categories (recovery score, sleep duration, strain, etc.) without needing further detail, since no annotations are present. Could mention that it is a read-only operation, but the description adequately implies safety.

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?

Three concise sentences: first defines purpose, second recommends usage, third lists outputs. No wasted words; every sentence serves a purpose.

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 provides sufficient context about what the tool returns. It covers the main use case completely for a daily check-in.

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?

Tool has zero parameters and schema coverage is 100%. Baseline 4 for no parameters; description adds no parameter info but none is needed.

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 a specific verb 'Get' and resource 'today's complete WHOOP status: recovery, sleep, and strain in one call.' It clearly distinguishes from sibling tools like 'get_recovery_trend' and 'get_sleep_trend' which focus on individual metrics.

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?

States 'This is the recommended daily check-in tool,' providing clear context for when to use it. Does not explicitly list when not to use or name alternatives, but the parenthetical mention of siblings implies those for detailed trends.

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