whoop_get_sleep_history

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

With no annotations provided, the description carries the burden of behavioral disclosure. It adds useful context about the data content (performance, duration, efficiency, stages) and multi-night scope, but it does not clarify 'recent' (which is governed by the limit parameter), authentication requirements, or rate limits.

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 a compact 9-word fragment that front-loads 'Recent sleep data' and uses a colon-separated list. It is concise and avoids waste, though it lacks a formal sentence structure.

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 2-parameter tool with no output schema, the description provides a reasonable overview of the returned data and multi-night scope. However, it does not explain how 'recent' relates to the limit parameter or explicitly differentiate from whoop_get_sleep beyond 'multiple nights', leaving room for improvement.

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?

The schema covers 100% of parameters with descriptions for limit and response_format. The description does not add parameter semantics beyond the schema, so the baseline of 3 is appropriate.

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 identifies this as a tool for retrieving recent sleep data over multiple nights, listing specific data fields (performance, duration, efficiency, stages). The verb 'get' is implied by the tool name, and the 'multiple nights' phrase distinguishes it from whoop_get_sleep.

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 use for multi-night sleep history but does not explicitly contrast with whoop_get_sleep or name alternatives. It gives context but no clear when-to-use or when-not-to-use guidance.

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