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

Annotations already cover readOnly/openWorld/destructive, so this is a safe read. The description adds material conduct context beyond annotations: a $0.05 USDC cost on Base, plan-key inclusion, and the percentile basis (4,000+ indexed wallets). This is genuinely useful for deciding whether to invoke a paid tool, though it omits latency/refresh behavior.

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 main payload (what is returned, interpretation caveat) is front-loaded, and the description is dense but largely waste-free. The payment line is slightly redundant, stating the $0.05 cost twice across two sentences.

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?

With no output schema, the description carries the burden of describing returns and does so: extraction history with percentile, deployer track records, and ENS/Farcaster identity. Combined with the cost and interpretation notes, an agent has enough to invoke it correctly, missing only explicit routing against siblings.

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?

Only one parameter exists and schema coverage is 100%, so the schema already documents 'token' as a 0x… contract address. The description adds no additional syntax or format meaning beyond that, so a baseline 3 is appropriate.

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 names a specific resource and scope: wallets in a token's notable holder set that have a measured off-market extraction/deployer record on Robinhood Chain. This is clearly distinguishable from a plain holder list or wallet lookup. It stops short of naming the sibling it should be chosen over (e.g., robinx_token, robinx_wallet), so differentiation is inferred rather than explicit.

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 gives interpretive guidance ('strong signal, ambiguous direction... not a buy call'), which helps the agent frame results, but it never states when to call this versus siblings like robinx_token or robinx_deployer. Usage is implied by the described output rather than prescribed.

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