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

Annotations cover read-only/open-world, and the description adds substantial context beyond them: the $0.02 USDC per-call cost, that failed calls are free, the two-step quote-then-pay flow, and the weekly freshness/source (Coinbase Bazaar). This is real operational disclosure with no contradiction of readOnlyHint.

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?

Well front-loaded: what it is, then pricing, then when-to-use, parameters and returns. Slightly redundant since the Returns line restates the opening enumeration, but the labeled sections make the redundancy cheap.

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 must carry return-shape burden and does: it lists the returned fields, plus pricing, failure behavior, quote flow, and data cadence. An agent has everything needed to call it correctly.

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 the example hostname and frames the payment parameter as a quote-first workflow with associated cost, giving meaning beyond the schema's bare 'Omit it to receive a quote'.

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 (look up) and resource (x402 seller by hostname) and enumerates exactly what comes back: rank, calls, revenue, wallets, endpoints, categories, competitors. This clearly distinguishes it from the broader x402_market_dataset sibling.

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 'When to use' line states the condition explicitly (you want ONE seller's numbers), which implicitly excludes the dataset-wide sibling. It stops short of naming that alternative or stating when-not-to-use, so it is clear context rather than full routing.

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