WHOOP Onboarding (shared wellness profile)

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

Annotations already declare readOnlyHint/idempotentHint, so the repeated 'Read-only' adds little. But the description adds genuinely non-structured behavior: the profile is shared across all Delx connectors, and it prescribes the next step (a separate update call with a specific flag). No note on freshness or failure modes, so not a 5.

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-loads the core action and payload, then the workflow, then cross-connector context. Well-structured, though the final connector digression is somewhat long for its value.

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 adequately describes what is returned (questions, profile state, missing fields). Combined with the explicit follow-up workflow and sharing semantics, an agent has everything needed to invoke and sequence this tool correctly.

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 50%; locale has its own enum description, while response_format is undocumented in both schema and description. The description's 'English or pt-BR' merely restates the locale enum. Baseline 3 is appropriate since the schema carries most of the weight.

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?

States a specific verb (Return) and resource (the 11-question Delx wellness onboarding flow) plus the supplementary payload (shared profile state, missing critical fields). It clearly distinguishes itself from siblings like whoop_profile_get and whoop_profile_update by naming them explicitly.

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 an explicit workflow: ask questions one-by-one, then call whoop_profile_update with explicit_user_intent=true to save. It also names the {connector}_onboarding alternatives and explains when relying on this one instead is acceptable.

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