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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context beyond the schema: it discloses the CLEAR/REVIEW/HOLD decision framing, the specific screening sources, and a fixed price of $0.45 USDC via x402. No contradiction with annotations.

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 compact and front-loaded: the bundle identity, outcome types, core checks, and price are conveyed in two sentences with no filler. Every clause adds decision-relevant information.

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 read-only, non-destructive screening tool with no output schema, the description adequately covers purpose, checks performed, decision outcomes, and cost. The only minor gap is that it does not clarify the alias relationships among the five required parameters, but those are already documented in the input schema.

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. The description adds meaning by connecting parameters to their screening purpose: party/name to US CSL screening, country/destination to embargo checks, and commodity to export-control flagging. This explains why each parameter matters, not just what it is.

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 states a specific, multi-part purpose: a one-call export/import pre-screen that screens the counterparty against US CSL, checks the destination against US embargo lists, and flags export-controlled commodities, returning CLEAR/REVIEW/HOLD. The 'bundle' label and decision outcomes clearly differentiate it from sibling screening tools.

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 clear context for when to use it: when an export/import clearance pre-screen is needed in a single call. It implies it replaces separate party, sanctions, and commodity checks, though it does not explicitly name sibling alternatives or state when not to use it.

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