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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower, yet the description adds substantial operational context: the 20,000 curve-trade analysis cap, $0.01 per call pricing, a 10 free/day quota, a payment-required result listing x402 options, and that isError responses for invalid input or upstream failure are not charged. The only missing piece is anything about result shape or latency, which the output schema covers.

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?

Dense but well front-loaded: purpose first, then scope, then when-to-use and alternatives, then pricing and error semantics. Every sentence carries information, though the paragraph is long enough that a reader must scan multiple clauses to find the pricing and error facts.

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?

For a read-only analytical tool with only two parameters, an output schema that covers return values, and full annotation coverage, the description supplies everything else an agent needs: scope, alternatives, cost model, quota, and failure semantics. Nothing material is 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%, so both parameters are already fully documented, making 3 the baseline. The description's mention that analysis covers 'the last 20,000 curve trades' adds a modest qualifier about what the limit actually counts, but it does not exceed the schema materially.

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 ('Any wallet's pump.fun trading record') and enumerates the exact outputs (realized PnL, win rate, hold time, bot/human classification, launched tokens). It is clearly distinguishable from siblings like pump_dev, pump_token and smart_money because it is a per-wallet performance profile.

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?

Explicitly states when to use it ('For a trader's pump.fun performance') and names two alternatives with the conditions that select them: counterparty_check for a quick deal/no-deal verdict, copy_backtest to test whether copying pays. The named alternative even carries a server/URL reference, leaving nothing to inference.

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