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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds no behavioral context beyond that – nothing about how matching/scoring works, source freshness, or rate limits. Adequate but thin against a lower bar.

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 short sentences with zero filler; the operational scope is front-loaded and the use case follows. Nothing is redundant with the name or the schema.

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?

Annotations and full parameter coverage make the call itself unambiguous, but there is no output schema and the description says nothing about what a match result contains (score, matched list entry, source). For a screening tool that gap is noticeable, though not fatal.

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%: address, limit, sources, and threshold are each documented in the schema itself. The description mentions 'listed addresses' only generically and adds no syntax, format, or threshold guidance. Baseline 3 is correct when the schema does all the work.

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 and resource: 'Match a physical address against listed addresses.' This clearly separates it from name-based screening siblings, though it never explicitly names sanctions_screen_entity or sanctions_screen_batch as the alternatives. An agent can infer the distinction from the word 'address' alone.

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?

Provides a concrete when-to-use condition: KYC / supplier vetting where the counterparty name is generic but the address is distinctive. That is genuine routing guidance, but it stops short of naming the sibling tool to use for name-based screening or stating any exclusions.

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