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

Annotations already cover the read-only/idempotent/open-world safety profile, and the description adds substantial context beyond them: per-call pricing of $0.01 USDC via x402 on Solana, a documented HTTPS alternative endpoint, data provenance (official files, no aggregator), and that matching is transliteration-aware fuzzy. No contradiction with readOnlyHint or openWorldHint.

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 core action and sources, then matching behavior, then return fields, then price/endpoint. Dense but every element is functional; the trailing pricing and URL sentences are operationally necessary rather than 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?

There is no output schema, and the description compensates by enumerating the returned fields (list source, programmes/regimes, aliases, DOB, countries, listing date, list publication date). Combined with pricing, alternative transport, and matching semantics, an agent has everything needed to call and interpret it.

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; the description earns above that by explaining the matching engine (transliteration-aware fuzzy, any order, Latin or Cyrillic) and 'scored matches', which gives the agent the mental model behind minScore and the name input. It doesn't elaborate on how lists/minScore interact, keeping it just short of 5.

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 of a person or company NAME') and enumerates the exact list sources (OFAC SDN/non-SDN, UK, EU FSF, UN). It is unmistakably distinct from every sibling tool (no other sanctions/compliance-listing tool exists in the sibling set).

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?

Clear context for when to reach for it — name screening against official consolidated lists, explicitly noting official files rather than a third-party aggregator, which is a meaningful selection criterion for compliance use. It does not state exclusions or point to any alternative tool, 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.