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

Annotations already declare readOnly/idempotent/openWorld, and the description adds material behavior beyond them: the $0.50 per-batch price, the x402/USDC-on-Base payment mechanism, and the fact that it returns payment requirements unless payment_signature is supplied. That payment-gate behavior is the single most important thing an agent must know and it is disclosed. It doesn't cover failure modes or partial-batch behavior.

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-loaded with a category tag, then purpose, then usage, then price/payment behavior and a sample link. Sentences are short and each carries distinct information, though the bracketed category tag and sample path are slightly ornamental.

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?

No output schema exists, but the description explains the critical return branch (payment requirements vs. results once payment_signature is given). For a paid batch tool this is nearly complete, leaving only the paid-response shape undescribed.

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 every parameter (names formatting, min_score range, matches_per_name range, payment_signature, include_export_control) is already documented in the schema. The description only restates the 100-name cap, adding no semantics beyond structured data. 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 action and scope: screen a whole list of customers/suppliers/payees against sanctions and US export-control lists 'in one call'. The batch framing ('whole list', 'up to 100 names') distinguishes it from the single-entity siblings screen_sanctions and screen_export_control, though it never names them explicitly.

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 clear usage context — 'onboarding backlogs or periodic re-screening' — which tells the agent when batch mode is appropriate. It stops short of stating when-not to use it or naming the per-name alternatives for one-off lookups.

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