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

Annotations already establish read-only, idempotent, non-destructive behavior, and the description adds valuable operational details beyond that: pricing at $0.005 per call, 10 free calls per day, payment-required x402 results, and error behavior with no charge for invalid input or upstream failure. These are exactly the behavioral traits an agent needs before invoking a paid 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?

The description is front-loaded with the verdict purpose, followed by classifications, usage guidance, alternative routing, pricing, and error behavior. Despite covering several operational details, every sentence earns its place and there is no redundant filler.

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?

Given the tool's complexity, annotations, parameter schema, and output schema, the description is complete enough to call correctly. It covers purpose, when to use it, the main alternative, pricing, payment-required behavior, and error handling; return-value details are unnecessary because an output schema exists.

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 the single wallet parameter is fully documented with type, pattern, and format in the schema. The description does not add further parameter semantics beyond what the schema already provides, so the baseline score of 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/resource and outcome: a one-call verdict on a Solana wallet, with concrete classifications like serial launcher, fast dumper, trading bot, or clean. It also distinguishes itself from pump_wallet for full trade stats, so an agent can identify the tool's role without opening the 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?

Explicitly says when to use it: before sending to or trading with a Solana wallet. It also names an alternative for a different need: use pump_wallet for full trade stats. This gives both positive usage guidance and an explicit routing alternative.

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