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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds the piece annotations cannot: a paid endpoint at $0.005/call, settled in USDC on Solana via x402, with a free-key alternative, plus a factual (not scored) output stance — useful disclosure that changes how an agent plans the call. It does not mention rate limits, latency or failure modes beyond payment.

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-loaded with the resource and its contents, and every clause carries information — no filler. It is a single dense run-on stitched with semicolons, which costs some parseability, but with no output schema the enumerated return contents are earning their space.

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?

No output schema exists, and the description compensates by enumerating the returned fields and the 90-day outcome buckets in detail. Combined with full schema coverage of both parameters and explicit payment/cost mechanics, an agent has everything needed to call it correctly and predict what comes back.

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%: the address parameter (base58 wallet address) and the payment/x402-signature parameter are fully documented in the schema, including the offer-on-omission behavior. The description only restates 'by wallet address' and 'no coin needed', adding nothing the schema does not already say, 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+resource — a pump.fun deployer's record by wallet address — and then enumerates exactly what the record contains (launches, graduations, best run, launch gaps, 90-day outcomes, newest launches, base rate for next launch). 'No coin needed' explicitly distinguishes it from the coin-keyed siblings like check_coin and find_coin, so an agent can route without opening a 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?

The 'For:' clause gives concrete query intents — 'this dev's history', 'a serial deployer', 'has this creator rugged before', 'the deployer's track record' — which map well onto how an agent would phrase a request. It stops short of naming an alternative sibling or stating when not to use it (e.g. vs. wallet_records or base_rate).

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