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

With annotations already covering readOnly/idempotent/non-destructive, the description adds real behavioral value: the $0.05 USDC cost, the specific screening providers and chain coverage, and the pre-transfer timing. It does not clarify the masked-vs-unmasked default result behavior, which is left to the parameter descriptions.

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?

Two dense sentences with the core capability and cost front-loaded and no wasted filler. Slightly marketing-toned ('Institutional') but efficient and well-ordered.

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?

Annotations cover the safety profile and the schema covers inputs, but with no output schema the description never indicates what a screening returns (score, flag, report) or how masked vs unmasked output differs. For a paid, gating tool that is a meaningful omission.

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 schema already documents address, x_api_key, and payment_signature, including the masked/unmasked unlock semantics. The description adds no parameter-level detail beyond what the schema provides, so the baseline of 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 verb (screens) and resource (0x EVM address) plus the concrete checks performed (AML, OFAC sanctions, phishing, mixer, malicious counterparty) and the data sources (GoPlus Security Base + Ethereum, 4-chain RPC). It is clearly distinguishable in intent from security_audit or wallet_profiler, though it never names a sibling to sharpen the boundary.

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 phrase 'before autonomous agents execute transfers' implies the trigger context, which is useful, but there is no explicit when-to-use vs alternative guidance and no when-not conditions. Usage must be inferred from the pre-transfer framing.

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