WHOOP wellbeing snapshot

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

No annotations provided, so the description must disclose behavioral traits. It indicates a read fetch (no destructive actions implied), but does not mention authentication, rate limits, data freshness, or side effects. The description is straightforward but lacks depth typical for a snapshot tool.

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?

Single sentence, front-loaded with verb and resource, lists components clearly. No filler or redundancy; every part 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?

For a simple fetch tool with no output schema, the description adequately lists return components. It could mention error handling or data availability, but the core output is covered. Minor gaps: no mention of how date is interpreted or whether all components are always present.

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?

Schema coverage is 100%, so baseline 3 applies. The description adds context for the date parameter ('for a date') but does not mention the includeRaw parameter or provide syntax details beyond the schema. No added meaning beyond schema fields.

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 verb 'Fetch' and the resource 'WHOOP snapshot', listing specific components (recovery, sleep, cycle strain, workouts, workload recommendation). This distinguishes it from siblings like whoop_sleep_summary (only sleep) or whoop_training_load_trend (only training load), making the composite nature explicit.

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?

No guidance on when to use this tool versus alternatives. With siblings like whoop_sleep_summary or whoop_training_load_trend, explicit when/why would help. The description only states what it does, not when it's appropriate.

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