whoop-get-user-profile

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

No annotations are provided, so the description carries full burden. It implies a read-only operation ('Get') and mentions it is for the authenticated user, but does not explicitly state behavioral traits such as non-destructiveness, authentication requirements, or any side effects. The description is adequate for a simple retrieval but could be more explicit.

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 a single sentence that is front-loaded with the main action ('Get basic user profile information') and includes key details. Every word is meaningful; there is no redundancy or filler.

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 has no parameters, no output schema, and is a simple data retrieval operation, the description is fully complete. It tells the user exactly what the tool does and what data it returns. No additional details are necessary.

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 input schema has zero parameters, and the description covers the schema completely. The description adds value by specifying the returned fields (name, email), which is beyond what the empty schema provides. According to guidelines, a baseline of 4 is appropriate for zero parameters when description adds context.

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 uses a specific verb 'Get' and identifies the resource as 'basic user profile information' with explicit fields (name, email). It clearly differentiates from siblings like whoop-get-user-body-measurements by indicating this is for basic profile data.

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 does not provide explicit guidance on when to use this tool versus alternatives. While the lack of parameters makes usage straightforward, there is no mention of exclusions or context for when one would choose this over other tools like whoop-get-user-body-measurements. It meets the minimum viable standard but lacks proactive guidance.

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