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

Annotations already declare readOnly/idempotent/openWorld/no-destructive, so safety is covered. The description adds genuinely useful non-structured behavior: pricing ($0.025/call, 10 free/day, x402 payment-required result) and error semantics (isError on invalid input or upstream failure, not charged).

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 benefit and 'When to use' are front-loaded, but the definition bloats itself by repeating the full sub-tool server URL and path three times for pump_token/pump_dev/pump_odds. That repetition adds length without adding decision-relevant information.

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?

An output schema exists, so return values need not be explained, yet the description still usefully summarizes the verdict categories (strong/neutral/weak/avoid). Combined with pricing and error behavior, an agent has enough to invoke and interpret the call correctly.

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 there is a single well-documented 'mint' parameter with a base58 pattern, so the schema carries the parameter meaning. The description adds no syntax or format detail beyond what the schema already provides, making the baseline 3 correct.

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 ('one call, one verdict on a pump.fun launch') and enumerates the concrete payload: 0-100 score, positives/risks, graduation odds, dev record, snipers, holders, flow. It also names the exact sub-tools it bundles (pump_token, pump_dev, pump_odds) so an agent understands it is an aggregator rather than a primitive.

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?

Explicit 'When to use' framing positions it as the one-call verdict and notes it is cheaper than calling the sub-tools separately, which is real routing guidance. It stops short of naming when NOT to use it or comparing directly to sibling token_risk, so it is clear context without exclusions.

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