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

Goes well beyond the annotations (which only cover read-only/idempotent/open-world) by disclosing the pricing model ($0.005 per call, 10 free/day, x402 payment-required result) and the error contract (isError with message for invalid input or upstream failure, and that failures are not charged). These are exactly the behavioral facts an agent needs before calling a paid, open-world tool.

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 verdict, then usage, price, and error behavior in a single dense paragraph; every section carries information. It is slightly overstuffed with parenthetical server/URL detail, which keeps it from a 5.

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-shape explanation is not required, and the description still summarizes what the verdict contains (risk level and reasons). With annotations covering the safety profile and pricing/errors covered explicitly, an agent has everything needed to call this 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 coverage is 100% and there is only one parameter, whose pattern and Base58 format are fully documented in the schema. The description adds only the framing that the wallet is a Solana counterparty, which the schema already implies — 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?

States a specific verb and resource — 'One-call verdict on a Solana wallet' — and enumerates the outputs (serial launcher, fast dumper, trading bot, clean) plus the inputs combined (pump.fun launch history + trading profile). It also distinguishes itself from the trade-stats tool (pump_wallet) and, by scope, from siblings like token_risk or address_check.

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: Before sending to or trading with a Solana wallet', and it routes the agent elsewhere for a related need ('for full trade stats use pump_wallet'). The trigger condition and the alternative are both named, leaving little to inference.

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