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

With no annotations, the description carries the full burden and does disclose meaningful behavior: matching is exact (not fuzzy), coverage spans every digital-currency address OFAC publishes across EVM/Tron/Bitcoin, and the result includes the sanctioned entity, program, and list publish date. It omits freshness/caching, rate limits, and any auth or cost caveat beyond 'Free'.

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 sentence block is duplicated verbatim in the description, roughly doubling its length with zero added information. The example is useful, but the repetition is pure waste in an otherwise short definition.

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 convey return content, and it does name the returned fields (entity, program, publish date). With one well-documented parameter and a clear scope, an agent has enough to invoke it correctly; only auth/rate-limit context is absent.

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 single 'address' parameter is fully documented in the schema, so the baseline is 3. The example URL reinforces the expected address shape but adds no syntax beyond what the schema already states.

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 states a precise question ('Is this address on the US Treasury OFAC SDN sanctions list?') and specifies exact-match semantics against OFAC's published digital-currency addresses, chain-agnostic. That is a specific verb+resource an agent can act on. It does not, however, differentiate itself from the sibling wallet_check or sanity_check tools.

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?

Usage is implied by the sanctions-screening framing, and 'Free' hints at a cost consideration, but there is no explicit when-to-use vs alternatives statement and no when-not-to-use guidance (e.g. fuzzy/near-match screening would need a different tool).

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