WHOOP training load trend

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

No annotations are provided. The description only states it returns trends, but does not disclose that this is a read-only operation, does not mention authentication requirements, rate limits, or what the return format looks like. Minimal behavioral information.

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 sentence with no wasted words. It front-loads the action ('Return') and resource ('trends') and succinctly lists the metrics. Every word 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?

With no output schema, the description should explain what the returned trend data contains (e.g., averages, slopes, time spans). It does not define the windows or how date interacts. Given 3 optional parameters and no output schema, the description leaves significant gaps in understanding the tool's behavior.

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%, with descriptions for all three parameters (date, shortWindowDays, longWindowDays). The description does not add extra meaning beyond listing the metrics; it does not elaborate on parameter usage or constraints. Baseline 3 is appropriate since schema already describes params.

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 returns short and long window trends for multiple specific metrics (sleep, sleep performance, recovery, HRV, resting heart rate, day strain). It distinguishes from sibling tools like whoop_sleep_summary (which provides a single point summary) and whoop_baseline_profile (which provides baseline values).

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 explicit guidance on when to use this tool versus alternatives. The description implies it is for trend analysis, but does not state when not to use it or mention sibling tools for different use cases (e.g., snapshot vs trend).

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