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

With no annotations, the description carries the load well: it discloses the output fields (listed yes/no, SDN entry, programs, network, list as-of date, data age), a legal caveat ('Not a legal determination'), and the payment/auth model ($0.0045 USDC via x402). It omits error behavior and any rate limits, so it falls short of exhaustive.

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 usage trigger, then labels Input/Output and closes with pricing — a clear structure. Most sentences earn their place, though the example URL is terse and the price sentence borders on promotional.

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, so the description must describe returns, and it does so thoroughly (listed flag, SDN entry, programs, currency/network, link, as-of date, data age), plus input formats, caveat, and cost. 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 description coverage is 100%, and the schema already explains both address and chain, including the EVM/BTC/TRX/SOL formats and the optional-chain behavior. The description largely restates this, adding only the 'EVM matched on every EVM chain' nuance, 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: checking a crypto wallet address against OFAC's digital-currency SDN list. The scope ('digital currency addresses') implicitly distinguishes it from the sibling sanctions_screen, which covers name/entity screening, so an agent can tell the two apart.

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 trigger condition: 'use when an agent must check a crypto wallet ... before paying or accepting funds.' It does not explicitly name sanctions_screen as the alternative for non-address screening, so the when-not case is only implied by the input type.

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