get_whoop_profile

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered and the bar is lower. The description contributes a meaningful extra signal by flagging the result as 'Sensitive identity data', warning the agent about privacy handling, but it says nothing about authentication scope, whether the member is the token owner, or error behavior when no profile exists.

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 short sentences, front-loaded with the action and followed by the risk note, with no wasted clauses. The adverb 'Explicitly' is slightly ambiguous filler, keeping this just short of a 5.

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 zero-parameter read tool whose annotations fully cover the safety profile, the description supplies enough: what it returns and why to be careful with it. Without an output schema, more detail on the exact profile fields would help, but nothing essential for correct invocation is missing.

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 tool takes zero parameters, so the baseline is 4 and there is no parameter meaning for the description to add. The brief mention of 'name/email' gives a hint of payload content, which is a small bonus rather than a gap.

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 a specific verb and resource ('retrieve WHOOP member profile') and names the key fields returned (name/email). The resource is clearly distinct from the sibling tools, which all deal with cycles, recovery, sleep, workouts, or summaries, so an agent can tell this is the identity/profile getter without opening the schema.

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 word 'Explicitly' implies this should be called deliberately rather than as part of routine data pulls, which is a useful nudge given the sibling list is full of bulk-listing tools. However, it never states when to prefer this over other profile-adjacent calls or any prerequisites, so usage remains inferred rather than specified.

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