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

With no annotations, the description carries the full burden and does substantial work: it discloses cost and payment rail ($0.01 USDC on Base or Solana via x402), validation behavior ('unknown formats refused before payment'), output contents, and a legal disclaimer ('Not a legal determination'). It does not cover latency, rate limits, or failure semantics for partially-valid batches.

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 usage trigger, then input, output, caveat, example, and price in a tight sequence — every clause carries information. It is dense to the point of being crowded (formats, example addresses, pricing all in one paragraph), costing a bit of readability.

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?

There is no output schema, and the description compensates fully by enumerating return fields (per-address yes/no, detected chains, SDN entity, programs, summary counts, list date). Combined with the payment and validation details, an agent has everything needed to call it 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 the single parameter is already documented. The description still adds value by presenting the alternative POST JSON {addresses:[...]} body form and reinforcing the 1-50 mixed-chain constraint, which is more than restating the 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: screening many wallets at once (up to 50, mixed chains) against OFAC SDN wallet addresses. The 'many at once / bulk' framing cleanly separates it from the single-address sibling sanctions_address without needing to name it.

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?

Explicitly says 'Use when an agent must screen many wallets at once (payouts, counterparty lists)', giving concrete triggering scenarios. It lacks an explicit when-not or a named pointer to sanctions_address for single-address screening, 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.