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

Goes well beyond the readOnly/idempotent annotations by disclosing the paid model ($0.01 USDC per call via x402) and, critically, the degraded behavior when no wallet is present (payment terms and paid HTTP URL instead of a verdict). It also enumerates what the verdict covers and the return shape (SAFE/CAUTION/DANGER, 0-100 score, reasons), which is exactly the context an agent needs before incurring a 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?

Front-loads the verdict purpose, then the checks, then the cost and payment fallback — a sensible priority order. The parenthetical check lists are dense but each element is informative; only the 'Not financial advice' tail is marginal.

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 no output schema, the description still communicates the return values (verdict tier, score, reasons) and the non-verdict payment response. Cost, scope, and failure mode are all covered, leaving nothing an agent needs before calling it.

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?

Single parameter with 100% schema description coverage including the address pattern and Base mainnet chain. The description adds no parameter-level detail beyond the schema, so the baseline of 3 applies.

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 deliverable ('Pre-trade risk verdict') for a specific resource (Base ERC-20), with a named target segment (brand-new Clanker/Zora/Uniswap v4 launches) and the checks performed. It doesn't explicitly contrast itself with the sibling get_token_info, which is the closest alternative, so it falls short of full sibling differentiation.

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?

Usage context is clear: pre-trade due diligence on freshly launched tokens, plus an explicit fallback path for MCP clients without an x402 wallet. It stops short of naming when-not-to-use or directing agents to get_token_info/explain_verdict_fields for narrower needs.

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