WHOOP Profile Get (shared wellness profile)

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false, and the description reinforces this with 'Read-only'. Beyond annotations, it adds the file path (~/.delx-wellness/profile.json) and details the returned fields, including 'missing critical fields', which provides useful behavioral context. No contradiction with annotations.

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 three sentences, starts with the action verb 'Read', and packs essential details without fluff. Every sentence contributes useful information, making it appropriately sized and well-structured.

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 simple read-only tool with one optional parameter and no output schema, the description provides a solid overview: what it reads, where it reads from, what it returns, and its non-mutating nature. It lacks explicit error handling or comparison to sibling whoop_get_profile, but these are minor gaps for such a straightforward tool.

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 only parameter, response_format, is defined by an enum with markdown/json and a default value, making its semantics clear from the schema. However, the description does not mention the parameter at all, and schema description coverage is 0%, so the description fails to compensate for the absence of a textual explanation. Since the parameter is optional and self-explanatory, the omission is minor but still present.

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 reads the shared Delx wellness profile and enumerates the contained fields, making the purpose specific. However, it does not explicitly distinguish itself from the sibling tool whoop_get_profile, which likely has a similar purpose, so it loses a point for not differentiating.

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?

The description notes the profile is cross-connector and available from other MCPs, implying this is one way to access the same data. It does not explicitly say when to prefer this tool over alternatives such as whoop_get_profile, nor does it mention criteria for choosing between connectors. The guidance is implicit, not explicit.

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