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

With no annotations, the description carries the full burden and does substantial work: it discloses the four outcome states (no_match, possible_match, confirmed_match, unable_to_determine) plus confidence, sources and matches, and it discloses the cost model ("Paid per call via x402 (USDC on Base)"). It does not cover rate limits, latency, or per-list coverage caveats.

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 sentences, front-loaded with the action and target, followed by return values and the use case. Slightly dense/promotional in the list enumeration, but every clause carries information an agent needs.

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 summarizes the return shape (verdict, confidence, sources, matches), which compensates. For a 6-parameter paid tool with no annotations, it is largely complete, though payment-flow mechanics (omitting payment_signature to fetch requirements) rest solely on the schema and no failure/timeout behavior is described.

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 the baseline is 3, but the description adds real meaning to the `lists` parameter by naming the 11 constituent lists and abbreviating them, which the schema only illustrates with "EL,DPL,MEU." The remaining parameters (limit, country, min_score, payment_signature) are left entirely to the schema.

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?

Specific verb+resource: "Screen a company or person name against the official US Consolidated Screening List," and it enumerates the constituent lists (BIS Entity List, DPL, MEU, ITAR Debarred, Treasury SDN/SSI/CMIC; 11 lists). No siblings exist to confuse it with, and the scope is unmistakable.

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 triggering scenario: "Use when selling, shipping or transferring goods, software or technology to a foreign party and you must screen it against US export-control and restricted-party lists." There are no sibling tools, so no alternatives need naming, but the description also states no when-not conditions (e.g. non-US list screening or name-clearing use cases).

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