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

Adds substantial context beyond annotations: the one-verdict output model, the specific screening signals, the $0.01/1-free-call-per-day pricing over x402, and the x-credit-token header auth path. Crucially, readOnlyHint=true is consistent — it screens but does not move funds — so there is no contradiction, and the pricing/auth detail is exactly the kind of operational context annotations cannot express.

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 core facts are present but the prose is dense and marketing-flavored, with a hook opener ('I'm about to pay 0x… $X — go?'), redundant re-emphasis of amount-awareness, and the filler disclaimer 'Identity is not intent; not financial advice.' Several clauses could be trimmed without losing actionable information.

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 explained, and the description still covers screening criteria, pricing, auth, and the verdict set. It would be fully complete with an explicit pointer to the alternative recipient-check tools for non-payment contexts.

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 the schema already documents both 'to' and 'usd'. The description mostly restates this ('Pass usd= for amount-aware guidance', 'Required input: to') rather than adding new syntax or format detail, landing at the baseline for a fully-covered schema.

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+scope: a pre-payment gate that screens a USDC recipient before an agent sends funds. It names the exact checks performed (OFAC sanctions, Coinbase/Basename identity, wallet vs contract, fresh-address age) and the output (GO/REVIEW/STOP), so an agent can distinguish it from siblings like address_check, safe_to_send, or sanctions.

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?

Clearly establishes the when-to-use scenario ('an agent about to send USDC', escalating fresh/anonymous recipients to STOP once the amount is material) and explains the amount-aware sampling-vs-drain logic. It does not explicitly name alternative siblings (e.g., address_check or pre_trade_gate) or state when NOT to use it, so it falls just 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.