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

The description adds important behavioral context beyond annotations: this is a paid x402 call costing 0.01 USDC and requires an X-Bazaar-Key header. It also lists the specific screening dimensions performed, which helps the agent understand what the call actually does. It does not contradict the annotations, though it could say more about what happens on payment failure or invalid key.

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 dense sentence that front-loads the payment requirement and then enumerates the bundle contents. It is appropriately sized for a multi-check tool, though the long run-on structure makes it slightly harder to scan than a bulleted or split presentation.

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 does an adequate job naming the composite risk_score and risk_breakdown, but it does not clarify insufficient-input behavior when zero required parameters are supplied, nor does it distinguish when to use url versus address versus payTo. That leaves a meaningful gap for an agent deciding how to invoke 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?

Schema coverage is 100%, so the schema already documents that address, payTo, and url are alternative target identifiers. The description does not add meaning beyond the schema, such as whether one of the three is required despite all being optional. Baseline 3 is appropriate when the schema carries parameter documentation.

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 names a specific verb/resource: a combined Base wallet and x402 seller risk bundle, and enumerates the concrete checks it performs (OFAC screening, first-funder trace, proxy inspection, seller profile, composite score). It is clearly distinguishable from narrower siblings like ofac_check or get_reputation because it explicitly bundles those capabilities.

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 'in a single call' implies this is the bundled alternative to separate checks, but the description never explicitly says when to use this bundle versus ofac_check, live_ofac_sdn_status_attestation, certify_seller, or get_reputation. Usage is implied rather than stated.

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