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

Annotations declare the safety profile (readOnly, idempotent, non-destructive, openWorld), and the description adds substantial context beyond them: pricing ($0.01/call over x402 on Base), the prepaid x-credit-token header option, one free call/day, no wallet or API key needed, and the single GO/REVIEW/STOP return shape. This is rich behavioral disclosure that the annotations do not cover.

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 content is dense and mostly earns its place (pricing, access, verdict semantics, freshness logic), but the conversational preamble 'I'm about to pay 0x… $X — go?' and the identity/not-financial-advice disclaimer add noise. Front-loaded framing is engaging but not maximally information-dense.

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 values need not be spelled out; the description still summarizes the single verdict. With annotations covering the safety profile and the description covering pricing, auth mechanism, and screening categories, an agent has everything needed to decide and invoke 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%, so both parameters are already documented, including that usd is optional and sharpens the verdict. The description reinforces that 'to' is required and that amount matters, but adds no syntax or format detail beyond the schema, so the 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?

The description states a specific resource and action: a pre-payment gate that screens a USDC recipient before an agent sends funds, and it names the dimensions screened (OFAC, Coinbase/Basename identity, wallet vs contract, address age). It differentiates itself functionally as 'amount-aware' from generic address-check siblings, but it never names an alternative tool, so it falls short of the explicit sibling-disambiguation that earns a 5.

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?

It gives clear context: call this when about to pay, pass usd= for amount-aware guidance, and it explains the escalation logic (material amount + fresh/anonymous recipient = STOP). The sampling-vs-drain framing is genuine when-to-worry guidance, but no when-not or named alternatives are given.

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