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

Annotations cover the read-only/idempotent/non-destructive profile, but the description adds substantially more: cost ($0.02 USDC via x402), the settlement rule (only charged when a result is returned; 400 and upstream 4xx/5xx are not settled), graceful degradation (a source that can't be reached is reported as failed rather than failing the call), and the 'screening aid, not legal advice' caveat. This is unusually rich behavioral disclosure.

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?

Front-loaded with the three guiding questions, then what the call runs, then return shape, then alternatives and pricing. It is long and dense, but nearly every clause carries distinct information (sources screened, cost, settlement, failure semantics). Minor compression possible in the source enumeration.

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?

No output schema exists, and the description fully covers return values (verdict block/review/clear, one-line summary, per-reason provenance, underlying facts). Combined with the failure-handling and billing notes, an agent has everything needed to call and interpret it.

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 baseline is 3, but the description adds real meaning: it clarifies that name is both OFAC-screened and used for a company lookup, that domain accepts a URL or email, and that wallet is the pay/receive address (e.g. an x402 payTo). The combination logic ('and/or') for otherwise-optional parameters is genuinely useful beyond the schema.

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?

Opens with three concrete user questions ("Is it safe to pay this vendor?", onboarding, payTo attribution) and states exactly what one call runs: OFAC screening, company profile, domain/email checks, and on-chain wallet risk. It explicitly names the four siblings it replaces (sanctions_screen, company_profile, domain_enrich, wallet_risk_check), so an agent can distinguish it without opening a schema.

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?

Gives explicit when-to-use scenarios (vendor onboarding, KYB, payee vetting before x402 or USDC payment, fraud screening) and names the exact alternative tools it consolidates. The 'and/or' combination of name/domain/wallet is described, so the agent knows how to compose inputs.

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