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

Annotations already declare readOnly/idempotent/non-destructive/non-open-world, so the bar is lower, but the description adds real interpretive value: matches are 'possible' fuzzy name matches, require manual review, and a no-match is not clearance. That is exactly the behavioral context an agent needs to avoid over-trusting results.

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-loads the matching scope and sources in one sentence, then a second sentence carries the caveats. No filler, though the source enumeration is dense. Every sentence earns its place.

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?

With no output schema, the description correctly fills the gap by noting results include 'match type and dated sources,' and it warns about the limits of matches/no-matches. The one unaddressed item is input format for the name parameter.

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 0%, so the schema documents nothing about the single 'name' parameter. The description only implies the input is a supplier name to screen and gives no format hints (e.g., whether Chinese characters are accepted, despite the CN/HK match discussion). Minimal compensation for the coverage gap.

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 (screening/matching) and resource (supplier name) and enumerates the exact reference lists checked (UK Sanctions, CN/HK US Consolidated Screening List, UFLPA). This distinguishes it from sibling tools like check_export_market or find_duty_rate, which are trade-compliance but not name screening.

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 signals this is an 'automated name check, not legal advice' and that a match needs manual review, which implies the appropriate framing of use. However, it never states when to choose this over sibling checks or any prerequisite (e.g., that a name is required), so usage is only implied.

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