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

With no annotations, the description carries the full burden, and it does disclose meaningful behavior: the $0.01 USDC-on-Base price, the x402 payment mechanism via params._meta['x402/payment'], and the GET endpoint. However, it does not say whether at least one of name/domain must be supplied, what happens when only one is provided, whether failures are still billed, or any rate limits — important gaps for a paid mutation-free network call.

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 bundle contents are front-loaded in the first clause, followed by cost/payment mechanics and the HTTP endpoint. Every sentence carries operational information, though the raw URL and CAIP-2 chain ID are slightly heavy for a description field.

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?

For a paid, no-annotation, no-output-schema bundle aggregating three data sources, the description covers what is computed and how to pay, which is the essential minimum. It omits input-validation behavior (what happens with name only vs domain only) and does not describe the roll-up risk-level scale, leaving an agent unable to interpret results confidently.

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 0%, so the schema documents neither 'name' nor 'domain' beyond their type. The description partially compensates by implying domain feeds the RDAP lookup and name feeds the sanctions/EDGAR match, and it documents an off-schema payment parameter (params._meta['x402/payment']) that the schema omits entirely. It still leaves requiredness and input formats unstated.

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 the resource and enumerates exactly what the bundle does: sanctions screening across US/GB/EU, SEC EDGAR company matching, and RDAP domain facts with a roll-up risk level. It is clearly a bundle, not a single lookup. It stops short of distinguishing itself from near siblings such as check_sanctions__screen, check_sanctions__entities, or company_facts__risk, which an agent would otherwise have to guess between.

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?

Calling it a 'One-call KYB bundle' implies the use case of consolidating separate sanctions, EDGAR, and RDAP lookups into one paid request, but the description never states when to prefer this over the individual sibling tools or any precondition. Usage is inferable rather than specified, and there are no exclusions.

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