x402_top_sellers

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

With no annotations, the description carries the full burden and largely meets it: it discloses the $0.01 cost, the accepted payment rails (USDC on Arc/Base/Solana, XNT on X1), the 6-hour refresh cadence, and the required two-call payment negotiation. It omits error/refund behavior and rate limits, keeping it short of 5.

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 what-is-it clause is front-loaded, followed by cost and the payment procedure in a tight three-sentence block. Dense but each sentence carries information; no filler.

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 one-parameter paid query tool with no annotations and no output schema, the description covers what it returns (seller hosts ranked by strongest listing with returning buyers), cost, cadence, and the payment flow. Only the exact response shape and failure modes are left unstated, which the absence of an output schema makes forgivable.

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?

There is only one parameter and schema coverage is 100%, so the baseline is already high. The description goes further by explaining the deferred-payment pattern behind `payment` — fetch terms first, then resend with a signed payload — which adds meaning beyond the schema's field description.

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 states a specific verb and resource (seller hosts on Coinbase's Bazaar ranked by strongest listing with returning buyers) and adds a distinctive ranking criterion. It is clear on its own, though it does not explicitly name which sibling (e.g., x402_bazaar_rank, x402_seller_rank, arc_seller_rank) it replaces for a given query.

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 concrete invocation guidance for the paid handshake (call without `payment` for terms, sign, call again with `payment`), which is genuinely useful. However, it says nothing about when to prefer this tool over the many ranking siblings, so selection guidance is only implied.

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