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

Annotations already cover the safety profile (readOnlyHint, openWorldHint), and the description adds substantial context on top: pricing ($0.10 USDC per call), that failed calls are free, the quote-then-pay flow, weekly rebuild cadence, and the Coinbase Bazaar data source. That is exactly the extra behavioral context annotations cannot carry.

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?

Two compact paragraphs with zero filler; the dataset contents lead, followed by the pricing/payment mechanics. Every sentence carries information an agent needs.

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, so the description compensates by enumerating the returned fields and category totals. Combined with pricing, freshness, and source, an agent has everything needed to call it and interpret the result.

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?

Only one parameter at 100% schema description coverage, so the schema already explains that omitting `payment` yields a quote and that the signed quote is resubmitted. The description restates this rather than adding syntax or format detail, so the baseline 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?

Specific verb ('Get') plus a precisely scoped resource ('the whole x402 market as one dataset') and an enumeration of returned fields (rank, 30-day calls, revenue, paying wallets, categories, labels, category totals). The 'whole market' framing implicitly separates it from the single-entity sibling x402_seller_lookup.

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 operational guidance on the payment flow ('call without payment to get a quote', failed calls cost nothing) but never states when to choose this over siblings like best_x402_tools or x402_seller_lookup. Usage is only implied by the 'whole market' scope.

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