Get Sleep Data

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful context about returned data fields (e.g., sleep stages, respiratory rate), but does not disclose potential behavioral nuances like pagination behavior, rate limits, or authentication requirements.

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 well-structured with a clear purpose sentence, labeled parameter list, and return-field bullets. It is slightly verbose but every section earns its place, and the formatting aids scannability.

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?

The tool has no output schema, so the description compensates by detailing expected return fields and parameter behavior. It covers key aspects for invocation, though it omits minor details like sorting order or error handling, which are not critical for this simple read-only tool.

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 description coverage is 100%, with each parameter already described in the schema. The description adds slight clarification (e.g., 'Filter sleeps after this date' vs 'End date filter') but does not significantly add beyond the schema. Baseline of 3 is appropriate given the schema carries the full parameter meaning.

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 detailed sleep data from Whoop, listing specific fields like sleep stages, performance, and respiratory rate. This distinguishes it from sibling tools focused on other data types (workouts, recovery, etc.) with a specific verb and resource.

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 implies usage (use when you need sleep data) but does not explicitly mention when not to use it or alternatives among sibling tools. It provides no exclusionary guidance or comparison to other Whoop endpoints, leaving the agent to infer appropriateness.

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