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

With no annotations, the description carries the full burden, and it discloses key behavior: public access, no bearer required, fuzzy matching, top-N results, and a 0..1 similarity scale. It stops short of rate limits, pagination, or any statement about side effects, though a screening call is clearly read-oriented.

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?

Three front-loaded sentences cover action, dataset, output shape, workflow trigger, and authentication, with no filler. Every sentence adds operational value.

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 includes source data, use case, output shape, similarity scale, and auth requirements, so an agent has enough to call it correctly. Minor gaps remain: no guidance on interpreting similarity thresholds, no pagination/rate-limit detail, and no output schema to compensate.

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?

The schema documents query, limit default, and country format; the description adds meaning by explaining fuzzy matching, top-N ranking, and the data categories behind topic enum values (sanction, PEP, crime). The topic parameter itself still lacks a direct description, but the prose compensates partially.

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 names a specific verb and resource: fuzzy-match a name against the OpenSanctions consolidated dataset, and it enumerates the exact list types (EU/US/UK/UA/UN sanctions, PEP, crime). That concrete scope distinguishes it from check_dual_use and the product/HS-code siblings even without naming them.

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?

It explicitly says to use it BEFORE signing a CartMandate, so the buyer agent can refuse a counterparty with sanctions/PEP exposure. It does not, however, state when not to use it or name an alternative such as check_dual_use for export-control screening.

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