Get WHOOP Profile

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

The description adds the behavioral trait of requiring a specific auth scope, which is beyond the annotations (which only declare readOnlyHint, etc.). However, it does not disclose other behaviors such as caching or external calls. Given the rich annotations, this level of additional detail is adequate.

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 extremely concise, consisting of two short sentences that immediately convey the tool's purpose and a key requirement. No superfluous words, and the critical information is front-loaded.

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 an output schema and comprehensive annotations, the description is mostly complete. It covers the essential purpose and scope requirement. However, it could be improved by noting that this is the base profile call compared to more detailed profile tools (e.g., 'whoop_profile_get'). The presence of an output schema reduces the need to describe return values.

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 description does not elaborate on the two optional parameters (privacy_mode and response_format). The schema provides basic descriptions for privacy_mode but not for response_format. The description could have added guidance on choosing values but did not, resulting in insufficient semantic help beyond the schema.

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 action ('Get') and resource ('the authenticated user's basic WHOOP profile'), making the purpose obvious. However, it does not differentiate from the sibling tool 'whoop_profile_get', which could cause confusion.

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 mentions the required OAuth scope ('read:profile') but provides no guidance on when to use this tool vs alternatives like 'whoop_profile_get' or 'whoop_profile_update'. No explicit when-to-use or when-not-to-use advice is given.

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