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

With no annotations, the description carries the full burden. It explains the output fields and gating criteria, implying a read-only listing operation, but does not explicitly state non-destructiveness, authentication needs, or rate limits. It is adequate but not thorough.

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 under 60 words, front-loads key differentiators, and every sentence adds value. It is efficient and well-structured.

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's simplicity (2 params, no output schema), the description fully explains what the tool does, what it returns, and when to use it. It is complete enough for an agent to select and invoke correctly.

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?

Schema coverage is 100% with both parameters described. The description does not add new parameter-level detail beyond the schema; it restates the realizability score range. Per guidelines, baseline 3 is appropriate as extra semantic value is marginal.

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 Hyperliquid traders that are 'copyable and realizable', using specific gating criteria like copy-lag decay, de-leverage, and alpha-vs-beta, distinguishing it from raw leaderboard PnL lists. It also specifies the returned 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 explicitly advises use when needing 'vetted copy candidates, not noisy top trader lists', providing a clear use case. It does not explicitly mention alternatives or when-not-to-use scenarios beyond this, but it contextually implies the tool is for filtered, actionable results.

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