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

Annotations already declare read-only, idempotent, open-world behavior, so the safety profile is covered. The description adds real context the annotations do not: the x402 payment gate, the $0.02 cost, and the fact that the call returns payment requirements rather than results unless payment_signature is supplied. It still says nothing about rate limits or how results are shaped on a hit.

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 bracketed domain tag and the core action, then layers usage, pricing, and payment behavior in short sentences. Slightly dense with billing and sample-link housekeeping, but every sentence carries information and nothing is buried.

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, so the description carries the burden of describing returns, and it only covers the payment-requirements branch. An agent gets no picture of what a screening result looks like (match records, scores against min_score, list codes), which is the actual payload of a 6-parameter screening call.

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 six parameters (name, limit, lists, country, min_score, payment_signature) are already documented in the schema. The description adds no syntax or interpretation beyond that, so the 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 (screen) and resource (a buyer or consignee against US export-control lists), and the title pins it to the Consolidated Screening List. It is clear what the tool does, but it never names the neighboring screen_sanctions / batch_sanctions_screen tools, and the lists parameter (SDN, SSI) overlaps those siblings, so the boundary is left to inference.

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?

Gives an explicit trigger: 'Use when a deal may involve US-origin items or technology,' which is genuine when-to-use guidance tied to a business decision. It offers no when-not condition and no named alternative for non-US or sanctions-only checks, so the routing guidance stops one step short of complete.

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