Get Whoop User Profile

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds behavioral context by specifying that it operates on the authenticated user and lists the returned fields. No contradictions exist, and the extra detail about return values is valuable.

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 concise and efficiently structured, with a clear opening sentence, a bulleted list of return fields, and a brief usage note. Every sentence adds value without redundancy, making it easy for an agent to parse.

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?

Despite having no output schema, the description enumerates all return fields, clarifying what 'basic profile information' means. Combined with a clear purpose, usage hint, and good sibling differentiators, the description is complete for a simple zero-parameter read-only 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?

With zero parameters, the schema fully covers all inputs (100% coverage). The baseline for 0 parameters is 4, and the description does not need to elaborate on parameter mechanics. It appropriately focuses on outputs rather than inputs.

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 states the specific action ('Retrieves basic profile information') and the resource ('authenticated Whoop user'). It clearly differentiates from sibling tools, which all target different data types (recovery, sleep, workouts, etc.), by focusing on profile identity fields.

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 provides clear context for use: 'Use this to identify the user and personalize responses.' It does not explicitly mention when not to use it or name alternatives, but the implied contrast with sibling tools is evident. This meets the 'clear context, no exclusions' level.

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