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

The description adds meaningful behavioral context beyond annotations by disclosing the paid x402 mechanism and the specific attestation fields returned: active list count, digest, and refresh timestamp. Annotations already cover readOnlyHint=false, openWorldHint=true, idempotentHint=true, and destructiveHint=false, so the remaining transparency gap is modest.

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 a single information-dense sentence with no wasted language. The payment tag is front-loaded and the tool's two functions, attestation and screening, follow immediately.

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?

The description is adequate for identifying the tool and its payment requirement, and it explains the attestation return fields. However, with no output schema, it does not describe the screening result shape, such as whether screening returns a boolean, match details, or risk metadata, leaving an important gap for an agent invoking the tool.

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?

There is one optional parameter and schema description coverage is 100%, so the schema already explains that the address is an EVM 0x address or comma-separated addresses. The description mentions live EVM address screening but adds no syntax, optionality, or batching semantics beyond what the schema provides.

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 clearly states a specific resource and output: an OFAC SDN ruleset attestation with SHA-256 digest plus live EVM address screening. It does not, however, distinguish this tool from close siblings such as ofac_check or risk_bundle, so an agent cannot tell from the description alone when this tool is preferred.

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 a key prerequisite by stating the paid x402 / X-Bazaar-Key cost of 0.02 USDC, which implies this is a paid compliance call. It does not explicitly say when to use this instead of ofac_check, whether an address is required for screening, or whether calling without an address returns only the attestation.

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