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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds real context beyond that: the matching rules (case, accents, punctuation ignored; word-prefix match), the free-tier vs caller-API-key auth behavior, and the caveat that hits are leads rather than confirmed matches.

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?

Two sentences, both dense with information, with the matching rule and list scope front-loaded and the caveat/auth note trailing. No filler.

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?

All three parameters are documented and the tool's limitations are stated, which is enough to call it correctly. With no output schema, the description could have said more about what a returned hit looks like, but for a screening search the essential guidance is present.

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 baseline is 3, but the description earns an extra point by explaining the matching semantics of `name` (word-prefix, accent/case/punctuation insensitive) and by scoping results to current listings. It does not clarify that `list` is optional or how omitting it behaves.

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 operation (search) against a specific resource (current US OFAC, UK and EU sanctions listings) with the matching rule spelled out. The word 'current' implicitly separates it from sanctions_list_changes and the search framing separates it from sanctions_entry, but no sibling is named outright.

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?

'A lead for screening, not a match decision: confirm against the official list' gives clear usage context and a hard constraint on how results may be used. It stops short of routing the agent to alternatives such as sanctions_entry for a specific record.

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