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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety bar is low; the description still adds real value by disclosing fuzzy matching, the score scale, and the explicit non-compliance disclaimer. It does not mention latency, list-freshness or rate limits, which a screening tool could reasonably be expected to flag.

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?

Front-loaded with the screening scope and sources, then inputs, then usage and caveat. It is somewhat dense and long but every sentence carries operational information; no filler or restatement of the title.

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 7-parameter tool with no output schema, the description helpfully sketches the return shape (score per hit, programme, list publication date) and the accepted subject types. It omits the fact that all parameters are optional but at least one of name/wallet is effectively needed, and says nothing about pagination or result caps.

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%, so the schema already documents kinds, lists, country, threshold and birth_date semantics. The description loosely reinforces the input shape ('optionally with country or birth date') but adds no syntax or interpretation beyond the schema, so the baseline of 3 applies.

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 verb+resource (sanctions screening) and names the exact data sources (OFAC SDN, EU consolidated, UK) plus what the tool returns (score per hit, programme, publication date). It also enumerates the two subject types (name vs. wallet address), which cleanly separates it from siblings like company, vat and domain.

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?

Gives explicit when-to-use context: 'screening a counterparty, supplier, customer or wallet before a payment or onboarding', plus a scope caveat ('screening aid, not a compliance determination'). It does not name an alternative sibling (e.g., due-diligence) or state when NOT to use it, so it falls short of a 5.

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