Connect WHOOP account

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

The description discloses one-time use, a 10-minute expiry, the need to open the link in a browser, the fact that it reads no WHOOP data, and the alternate behavior in stdio mode. This goes well beyond the annotations and is consistent with readOnlyHint=true.

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 front-loaded with the core result, then gives usage context, user instructions, and a caveat. Every sentence contributes necessary information without 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?

For a tool with no parameters and no output schema, the description fully covers invocation context, user action required, expected effect on other tools, and environment-specific behavior. Nothing an agent needs is missing.

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 tool has zero parameters and the schema already reflects that completely, so there is nothing for the description to add. This matches the baseline for a parameter-less tool.

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 names a specific verb and resource: it returns a one-time link that connects the user's WHOOP account. It also clearly distinguishes itself from the sibling data tools by stating it doesn't read any WHOOP data.

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?

It explicitly says when to use the tool: when a data tool reports WHOOP isn't connected or authorization has expired. It also covers the stdio-mode exception and explains the expected outcome, so the agent knows when it applies and when it doesn't.

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