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

With no annotations, the description carries the full burden of disclosing behavior. It does so well: it lists detailed risk flags, the three-level verdict, supported blockchains, cost per call, and authentication method (no API key, USDC over x402). It omits potential latency or failure modes, but the disclosed behavior is substantial and beyond just the tool's action.

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 front-loaded with the main purpose, followed by the use case and operational details. It is moderately detailed but not bloated. The second sentence is somewhat promotional ('should make before transacting') but still adds usage guidance. Overall, every sentence contributes value, though it could be trimmed slightly.

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?

There is no output schema, so the description must at least hint at the return value. It does so by stating the verdict types and listing risk flags. It also provides network coverage, cost, and payment method. It stops short of describing the exact response structure or error handling, but for a single-parameter tool, this is reasonably complete.

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?

The input schema covers the only parameter, x_payment, with a description of 'Signed x402 payment payload.' The tool description does not add any new meaning about this parameter beyond mentioning 'USDC over x402' which relates to payment but not the parameter's structure or usage. Since schema coverage is 100%, 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?

The description states a clear, specific verb and resource: 'Screen any wallet address for compliance and security risk in one call.' It enumerates the exact risk categories (sanctions/OFAC, money-laundering, phishing, etc.) and the output verdict (CLEAR / CAUTION / HIGH_RISK). This distinguishes it from general wallet or portfolio tools by focusing on compliance and security.

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 provides clear usage context: 'every payment, settlement, compliance, and trading agent should make before transacting with a counterparty.' This tells the agent when to use it, but it does not explicitly name alternatives or state when not to use it. The context is strong, so it earns a 4.

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