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

Annotations already state readOnly, idempotent, and not destructive. The description says 'lists', which is consistent but adds no additional behavioral details beyond confirming read-only nature. No contradictions.

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, clear sentence without unnecessary words. It efficiently conveys the tool's function and output fields.

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?

The description lacks critical context such as whether authentication is required, the return format (e.g., list of objects), error conditions, or how the result might be used. The unexplained parameter further reduces completeness.

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 only parameter 'account' is not explained at all. It is a string and optional, but its purpose (filter? identifier?) is unclear. Since schema coverage is 0%, the description must compensate but does not.

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 lists WHOOP accounts linked to the install and specifies the fields returned (account_id, name, email). This distinguishes it from sibling tools like whoop_profile or whoop_workouts.

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?

It indicates the accounts are linked to the install, implying a query for all associated accounts. However, it does not explicitly state when to use this versus alternatives or provide any usage context (e.g., retrieving account IDs for subsequent calls).

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