Connect WHOOP account

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

Goes well beyond the readOnlyHint and openWorldHint annotations: link is one-time, expires in 10 minutes, must be handed to the user to open in a browser, and it reads no WHOOP data. It also discloses two non-obvious edge-case behaviors — stdio mode returns setup instructions instead of a link, and an unconfigured WHOOP app returns its setup page address — which materially change how the agent should present the result.

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?

Front-loaded with what it returns, then the trigger, then the handoff instruction, then the caveats — a sensible priority order. It is a dense four-sentence block, but each sentence carries distinct operational information (expiry, browser handoff, stdio fallback), so little is wasted.

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?

Although there is no output schema, the description explains what comes back in every mode: a one-time link, stdio setup instructions, or a setup page address. For a zero-parameter auth tool with a single job, an agent has everything needed to call it and relay the result.

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 takes no parameters, so the empty schema is already complete and the description has nothing to disambiguate. Baseline for a zero-parameter tool; no syntax or format gaps exist to compensate for.

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?

Names a specific verb and resource — returns a one-time link that connects the user's WHOOP account — and immediately distinguishes itself from the sibling data tools by stating it doesn't read any WHOOP data. An agent can tell it is the auth/bootstrap tool, not a data retrieval tool.

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?

Gives the exact trigger: use it when a data tool such as get_today reports WHOOP isn't connected or its authorization expired, and names the post-condition (after login, get_today and other data tools work). Sibling tools are named as the source of the signal, so the routing decision is explicit.

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