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

Beyond the readOnlyHint/idempotentHint annotations, the description discloses that the call costs $0.01 USDC and appears to charge only on success, which is material behavioral information. It also clarifies that the data comes from on-chain Base USDC activity rather than seller claims.

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 two sentences long, leads with the core ranking purpose, and the second sentence adds the pricing caveat. There is no filler or repeated schema information.

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 low-complexity read-only tool with no required parameters, the description covers what is ranked, the data source, and the cost. It omits the exact return shape, but an agent can infer a ranked seller list from 'Which x402 sellers actually earn, ranked by...'.

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 100%, and the schema already documents limit and category clearly, including defaults and range/enum constraints. The tool description adds no parameter-level meaning, 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?

The description names the resource ('x402 sellers') and the ranking basis ('USDC read off Base — not by their own claims'), giving a specific, actionable purpose. The phrase 'ranked by USDC' also distinguishes this tool from sibling tools like x402_trending_services or x402_category_demand.

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 description gives no guidance on when to choose this tool over x402_market_report, x402_top_movers, or the other siblings. It does not state use cases, exclusions, or conditions under which another tool would be preferable.

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