WHOOP baseline profile

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

Without annotations, the description carries the full burden of behavioral disclosure. It only states a computation task but omits any behavioral traits such as whether it is read-only, requires authentication, or has rate limits. The agent cannot infer safety or side effects from the description alone.

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 single, front-loaded sentence that efficiently conveys the tool's action and scope. Every word contributes to understanding, with no filler or 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 lack of an output schema, the description should hint at the return format or structure. It does not, leaving the agent uninformed about what the baseline ranges look like. The description covers the input and purpose adequately but is incomplete regarding output.

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 the description adds no meaning beyond what the schema already provides for 'date' and 'windowDays'. While the schema includes defaults and constraints, the description does not elaborate on their significance.

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 the specific verb 'compute' and clearly states the resource 'personal baseline ranges' for five metrics (sleep, recovery, HRV, resting heart rate, day strain). It effectively differentiates from sibling tools like whoop_sleep_summary or whoop_training_load_trend by focusing on baseline computation rather than summaries or alerts.

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 provides no guidance on when to use this tool versus alternatives, no prerequisites, and no conditions for use. For example, it does not clarify whether this should be used for a specific window or if other tools are better for individual metric details.

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