WHOOP profile

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

Annotations already indicate readOnlyHint=true, confirming safety. The description adds that include_raw=true attaches raw records, providing some behavioral context beyond annotations. However, it lacks details on authentication requirements, rate limits, or response size.

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?

Two tightly written sentences with no unnecessary words. First sentence covers purpose and data returned; second sentence explains the optional parameter. Highly efficient.

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?

Given the tool's simplicity (one optional param) and presence of an output schema, the description covers essential usage. Could be slightly improved by explicitly stating the return includes standard profile fields, but overall complete.

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?

Despite 0% schema description coverage, the description explains the sole parameter include_raw: setting it to true attaches untouched profile and body-measurement records. This adds clear semantics beyond the schema's default value.

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 retrieves the user's WHOOP profile and body measurements, listing specific fields (name, email, height, weight, max heart rate). This distinguishes it from sibling tools like get_cycle or get_sleep that focus on other resources.

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 implies usage for fetching profile info, but provides no explicit guidance on when to use this tool versus alternatives like fetch or get_connection_status. No exclusions or alternative suggestions are given.

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