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

Annotations already declare read-only, idempotent, non-destructive behavior. The description adds meaningful behavioral context beyond that: pricing ($0.005 per call, USDC on Solana over x402 or a free key), how payment offers are returned if the payment field is omitted, and that the output is facts with no verdict. There is no annotation contradiction.

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 a single, very long run-on sentence with many nested parentheticals and a duplicated phrase ('whether one or one or two wallets'). It front-loads the basic purpose but lacks structural separation and is hard to scan, despite containing useful detail.

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?

There is no output schema, so the description carries the return-value burden and does so exhaustively: deployer record, bundle at creation, insider share, curve progress, market cap, SOL reserve, holders, top traders, and comparable-launch outcomes. It also covers payment flow and use contexts, leaving little an agent needs missing.

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 description coverage is 100%, and both parameters are documented in the schema: mint as the base58 coin mint and payment as the x402 PAYMENT-SIGNATURE. The description adds only the shorthand 'contract address, CA' and reiterates the payment model, so 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 states a specific verb and resource: check a pump.fun coin by its mint, and enumerates the facts returned. However, it does not distinguish this aggregate from overlapping siblings such as check_coin, deployer_record, or similar_launches, so an agent cannot tell exactly when this tool is preferred over those.

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 explicitly lists use cases: check this coin, a rug check, is this coin bundled, who holds it, who made money on it, who deployed this token, is this dev legit. It gives clear positive context but no when-not guidance or alternative routing to the many siblings that cover subsets of the same data.

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