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

Goes well beyond the readOnly/openWorld annotations: it discloses the two-call async pattern, first-call-is-free vs $0.03 pricing, plan-key inclusion, and ~10-60s latency. It also explains what a label means ('a wallet with no record carries no label') and the collapse of multi-wallet entities — behavioral detail annotations cannot express.

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?

Front-loads the resource and scope, and every clause carries real information (labels, verdict, two-call flow, cost). It is dense and packed with nested parentheses, which slightly impedes parsing, but little is wasted for a tool with this much behavior to convey.

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 complex tool with no output schema, the description compensates by describing the return content (per-wallet labels, structure verdict) and the full invocation lifecycle (queue, wait, recall, price). An agent has enough to call it correctly and interpret results.

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?

There is only one parameter and the schema already documents it fully at 100% coverage ('Token contract address 0x…'). The description only situates it as 'a Robinhood Chain token,' adding little syntax or format meaning beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource ('Labeled holder-structure diff for a Robinhood Chain token') and enumerates exactly what it produces: who froze/added/trimmed/exited plus a rotation-vs-distribution-vs-accumulation verdict. This distinguishes it from generic siblings like robinx_token or robinx_smart_holders without opening either 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?

Gives concrete operating guidance — 'first call queues the scan (free, ~10-60s); call again for results' — and hints at scope differentiation via 'the repricing-or-rug call price data cannot make.' It does not, however, explicitly name an alternative tool for related holder questions, so routing is implied rather than stated.

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