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

Beyond the readOnlyHint/openWorldHint/destructiveHint annotations, it discloses the matching method (deterministic normalized-name and token matching), the freshness fields returned (as_of, checked_at), the verdict taxonomy (CLEAR/REVIEW/HIT), and the full x402 payment sequence (402 → PAYMENT-SIGNATURE → delivery, $0.02 USDC on Base). This is exactly the payment/semantics context annotations cannot carry.

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?

Purpose is front-loaded and every sentence carries information (dataset, verdict, cost, payment flow). The one inefficiency is the opening sentence duplicating the title verbatim, and the payment/URL mechanics are packed densely into the tail.

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 no output schema, the description compensates by explaining what the agent gets back (x402 URL to GET, verdict, as_of/checked_at) and the full payment ceremony. Nothing needed to invoke or interpret the tool is missing for this scope.

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 coverage is 100% for the single 'name' parameter, and the description adds no syntax or format detail (e.g. casing, ordering, alias handling) beyond what the schema already states. Baseline 3 is appropriate when the schema does the heavy lifting.

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 and resource — screens a company/entity name against the OFAC SDN and Consolidated lists — and quantifies the dataset (~40k names + aliases) and the verdict scheme. This is clearly distinguishable from the sibling screen_sanctions_wallet, which screens an address rather than a name.

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 when to use it (a name/entity screening task) and gives useful operational context ('Free to call this tool; payment happens on the URL'), but it never names an alternative or states a when-not condition. An agent must infer the name-vs-wallet split from the sibling list rather than being told.

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