WHOOP Onboarding (shared wellness profile)

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

The description explicitly states 'Read-only', aligning with annotations (readOnlyHint=true, idempotentHint=true, destructiveHint=false). It adds context about returning missing critical fields and the shared nature of the profile, which is beyond what annotations provide.

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 paragraph with the main action front-loaded. It includes essential usage guidance without excessive verbosity, though it could be slightly more concise.

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 sufficiently explains the return value: onboarding flow, current profile state, and missing critical fields. It also mentions the 11-question structure and the locale options, making the tool's behavior clear for an agent.

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 already describes both parameters (locale and response_format) with enums and defaults. The description reinforces locale by mentioning English or pt-BR but does not add meaning for response_format. Baseline 3 is appropriate as schema coverage is high.

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 it returns the 11-question Delx wellness onboarding flow plus current shared profile state and missing critical fields, with locale options. It distinguishes itself from siblings by noting that other connectors have equivalent tools but this one is shared.

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?

Explicitly instructs the agent to ask questions one-by-one then call whoop_profile_update with explicit_user_intent=true. Also explains that agents can use equivalent {connector}_onboarding tools or rely on this one since all connectors share the same questions.

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