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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds genuinely useful context beyond that: the shape of each hit (list name, aliases, addresses, programs, FR notice, match score) and an explicit pricing model of $0.003 USDC per successful call via x402, with failed calls free. The cost/paid-call disclosure is important operational context for an agent.

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?

Three tightly packed sentences with zero filler: what it searches, what a result contains, and what it costs. The resource and scope are front-loaded before the return-content and pricing details.

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 100% schema coverage, an output schema present, and safety annotations in place, the description's remaining burden is light and mostly met (coverage of lists, result fields, and cost). The one gap is that it doesn't route the agent against overlapping screening siblings such as screen_debarment or sanctions.

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 all three parameters are already documented in the schema (range, default, ISO-2 examples). The description only echoes 'by name and optional country' and adds no format or constraint detail beyond the schema. Baseline 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 (Searches) and a precisely named resource (US trade.gov Consolidated Screening List), then enumerates the covered sub-lists (Entity List, SDN, Denied Persons, Unverified, ITAR Debarred). This distinguishes it from nearby siblings like screen_debarment and sanctions without opening any schema.

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 implies the use case (screen a name/entity against consolidated trade lists) and notes the optional country filter. However it never says when to prefer this over screen_debarment, sanctions, or enforcement_actions, and gives no exclusions or prerequisites. Usage is inferable but not explicit.

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