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

With no annotations, the description carries the full behavioral burden. It usefully discloses that matching is exact, what fields are returned, and the payment cost and rail (x402 on Base). However, it does not describe no-match behavior, error responses, or the full set of supported chains/assets, leaving meaningful gaps for a paid sanctions-check endpoint.

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 two tightly written sentences. It front-loads the purpose, then adds return information and payment details without unnecessary framing. Every element earns its place.

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?

For a single-parameter tool with no annotations and no output schema, the description covers purpose, exact-match behavior, return fields, and payment cost. It is nearly complete, but lacks no-match semantics and a definitive supported-asset list, which would be useful given the absence of structured behavioral metadata.

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 address parameter is already documented. The description adds meaningful context by listing supported address/asset types and emphasizing exact matching, which helps an agent understand what kinds of addresses are valid. It stops short of explaining normalization rules beyond what the schema already says.

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 gives a specific verb and resource: checking a crypto address for an exact match against OFAC SDN digital currency addresses. It clearly states the supported asset examples and what a match returns. It does not explicitly distinguish this from the sibling sanctions_screen tool, so it falls short of 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?

The description implies the tool is for OFAC crypto-address matching, but gives no explicit when-to-use guidance relative to alternatives such as sanctions_screen. It also does not state when-not to use it, such as for fuzzy matching or indirect exposure checks. The exact-match constraint is mentioned, but only as behavior, not as selection guidance.

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