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

Annotations only declare readOnlyHint and openWorldHint; the description adds critical non-structured behavior: a 0.01 USDC charge, the x402 payment rails (Solana or Base), and the exact field (_meta['x402/payment']) the caller must populate. Price, payment mechanics, and the paid-vs-free economics are all disclosed, which is exactly what an agent needs before incurring cost.

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 mandatory-cost warning is front-loaded in caps before any capability detail, which is the right ordering for a paid tool. Two sentences, no filler; the feature enumeration earns its place by justifying the charge and setting expectations.

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?

With one fully described parameter, no output schema, and minimal annotations, the description covers everything an agent needs: cost, payment channel, what is analyzed, and when to invoke it. Nothing required to call it correctly 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% for the single `mint` parameter (base58 SPL mint address, 32-44 chars), so the schema fully documents the input. The description restates the token type but adds no format or validation detail beyond it, 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 resource (Solana SPL mint) and enumerates exactly what the score covers: authorities, Token-2022 extensions, top-10 holder concentration, rugcheck flags, and a live Jupiter round-trip. The word "Full" implicitly distinguishes it from solana_token_quick_check, but the description never names either sibling, so differentiation is left to inference.

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?

"Use before swapping into an unknown token" gives a concrete trigger context for calling it. It stops short of when-not-to-use guidance or naming solana_token_quick_check/solana_token_safety_batch as cheaper/bulk alternatives, which matters because this is the paid tier.

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