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

With no annotations, the description carries the full burden, and it does so thoroughly. It discloses authentication and payment requirements, the two data sources, the 24-hour expiry, the signature from a ChainHelix key with no funds, and the three possible result values. It also notes the verification workflow expected of a seller agent.

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 description is a long, dense block that leads with payment mechanics rather than a crisp statement of purpose. The core definition appears only after the payment details, and the run-on structure makes it harder to parse. Useful content is present but poorly organized for quick agent scanning.

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?

The description covers authentication, payment, output contents, expiry, signature verification, and result semantics, and an output schema exists. However, the undocumented 'network' parameter is a notable completeness gap, and the payment complexity is high enough that a clearer structural breakdown would help. Overall adequate but not fully complete.

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 0%, so the description must compensate for both parameters. It explains that 'address' is an EVM address, but it never defines the 'network' parameter, which appears in the schema but is left entirely undocumented by both schema and description. This is a meaningful gap for a payment-bearing tool.

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 clearly states the tool's function: it returns a signed statement on whether a wallet is clear of sanctions lists, drawing on the OFAC SDN address list and an on-chain sanctions oracle. It identifies the resource (an EVM address) and the result (clear/listed/partial). It does not explicitly compare itself to sibling tools like buyer_clearance or wallet_risk, so it falls just short of full differentiation.

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?

The description gives clear usage context: this is the screen every payer passes before a settle, and a seller agent checks the signature and expiry before negotiating. This tells an agent when the tool is relevant. It does not name alternatives or explicitly say when not to use it, so it lacks full exclusion guidance.

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