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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds real context beyond them: batching cap of 50 addresses per call, $0.01 per-call pricing via x402 USDC, and the free-key alternative. It does not discuss failure modes for malformed addresses or latency, so it is strong but not complete.

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?

Purpose is front-loaded in the first clause and the fields list follows, with pricing/limits at the tail so an agent can stop reading early. The long parenthetical defining every class is dense but justified because there is no output schema to carry those definitions elsewhere.

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 return-value burden and does so by naming pnl_sol, put_in, took_out, coins, first_seen and recent, plus the class taxonomy. Payment acquisition and the batch cap are covered; the only gap is the exact response envelope and per-address error behavior.

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%, so the schema already documents all three parameters including mint's effect on the 'new' classification and payment's x402 offer flow. The description reinforces the batching limit and the mint-relative notion of 'new' but adds no syntax or format detail beyond the schema; 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?

The definition opens with a specific verb and resource ("Check pump.fun wallets by address") and then enumerates both the classification it returns and the fields behind it, so an agent knows exactly what comes back. It is distinguishable from siblings like deployer_record and top_wallets by being address-keyed lookup, though it never explicitly names those siblings to route between them.

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?

"For:" enumerates concrete use cases — who is buying this coin, is this wallet a bot, a wallet's PnL, a holder check on the top buyers — which gives an agent a clear trigger condition. No explicit exclusions or named alternative tools are given, so it stops short of full routing guidance.

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