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

Annotations already declare readOnlyHint=true and destructiveHint=false; the description adds meaningful behavioral detail: it screens 'with aliases', returns 'match/no-match, which list, programs, and a clear/review/hit verdict', and outputs JSON. It also discloses the bundled nature and price, going beyond the annotations and giving the agent a clear picture of results. Minor gaps remain (e.g., no mention of data freshness or interpretation of 'review'), but it is solidly transparent.

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?

The description is dense but well-organized: the core action and bundle concept lead off, followed by covered lists, output details, use case, format, and price. Every element is functional and there is no filler, though the long em-dash chain makes it slightly heavy to parse and could be split into cleaner sentences.

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 tool with only two parameters and no output schema, the description covers the essential context: the exact screening lists, the verdict format, the use case, and the output format. It is complete enough for an agent to decide to call it and interpret a basic response. It doesn't explain edge cases like name variations or ambiguity handling, but the provided detail is strong.

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 reinforces that 'name' is a person or company name, matching the schema, but it adds no new meaning for the 'type' parameter beyond what the schema already states. It does not compensate with extra format or usage details, so it stays at baseline.

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?

The description clearly states a specific action ('screen a person or company name') against a specific resource (US Consolidated Screening List) with named sub-lists and an output verdict. It is unambiguous about what the tool does, though it does not explicitly contrast itself with sibling tools like trade_party_screen or legal_reg_watch, so it just misses the top score for sibling differentiation.

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?

The description gives a clear usage context ('For KYC and onboarding') and specifies the applicable scope (sanctions/watchlist screening), which tells an agent when this tool is relevant. However, it does not state when not to use it or mention alternative tools, so it lacks explicit exclusions or comparisons.

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