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

With no annotations, the description carries the full behavioral burden and does substantial work: it discloses the measurement methodology (USDC transfers of $5 or less into each seller's payTo on Base), the temporal unit (one UTC day at a time, with the day it covers), and the access cost ($0.01 USDC via x402 on Base). It stops short of describing pagination, caching, or what happens when no sellers qualify.

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 hook question front-loads purpose, the metric list is packed into one clause, and the methodology and pricing sentences follow in a sensible order. The long enumeration of return fields is dense but each item is informative, with only mild redundancy in restating the ranking basis.

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, enumerating the returned metrics (revenue windows, payers, repeat share, wash flag, categories) is exactly the right compensation, and the cost note tells the agent this is a paid call. The remaining gap is the temporal semantics: it says 'one UTC day at a time, with the day it covers' but exposes no date parameter, leaving unclear which day is actually returned.

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%, with 'sort' enum values and 'limit' bounds fully documented in the schema, so the baseline of 3 applies. The description echoes the sort dimension ('ranked by measured revenue or paying wallets') but adds no constraint detail beyond the schema and never mentions the limit parameter.

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 uses a specific framing ('top Bazaar sellers on Base ranked by measured revenue or paying wallets') and enumerates the metrics returned, so the resource and ranking basis are unambiguous. It never names its closest siblings (x402_seller_stats, x402_market_summary), so the agent must infer the boundary from subject matter alone.

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 rhetorical opening ('Which x402 sellers actually earn?') implies the use case — leaderboard/discovery — but there is no explicit when-to-use or when-not-to-use guidance and no pointer to x402_seller_stats for per-seller drill-down. Usage is inferable rather than stated.

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