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

Annotations cover the safety profile (readOnlyHint, openWorldHint, idempotentHint=false), and the description adds material context beyond them: the categories screened, the verdict tiers, supported chains, and the $0.005 USDC price via x402 or prepaid credits plus free-trial availability. Cost and payment mechanics are genuinely useful operational detail. It does not explain why the call is non-idempotent or describe latency/rate limits.

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 core purpose and the trigger condition, but the first and second sentences are near-verbatim restatements of each other ('before you pay, trade with or accept funds from' repeated). The pricing/chains tail is compact and useful, but overall roughly a third of the text is redundant.

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-value detail is unnecessary. The description supplies the screening categories, verdict tiers, chain coverage, and cost model, which is enough for an agent to call it correctly. Minor gaps remain around what a 'suspicious' vs 'high-risk' verdict implies for action.

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 documented, including the chain enum list. The description merely re-lists the same chains rather than adding format guidance (e.g., address normalization per chain), so baseline 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 verb and resource ('screens a wallet or contract address'), enumerates the risk categories checked, and names the output verdict tiers. It does not distinguish itself from close siblings like wallet-report, wallet-deep, or token-safety, so an agent cannot tell purely from the text which wallet-related tool to pick.

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?

Gives a clear triggering context repeated twice: 'Before you pay, trade with or accept funds from an address.' That is a usable when-to-use condition. It offers no exclusions or named alternatives (e.g., when to prefer wallet-report or trade-precheck instead), so it stops short of full routing guidance.

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