x402_pricing

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

With no annotations, the description carries the full burden and does disclose the most important non-obvious trait: a $0.01 USDC charge per call via x402 on Base, deducted automatically from a configured wallet. It stops short of stating rate limits, caching, or whether failures are still billed.

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 sentences, front-loaded with the resource and the payload of metrics, followed by audience and payment terms. Dense but every clause carries information; the parenthetical payment method is useful rather than 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?

No output schema exists, and the description does compensate by enumerating the returned metrics. Missing pieces are the shape of the response (per-category list?), whether it covers all categories or a fixed set, and how it differs from the sibling x402_overview.

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?

The tool takes zero parameters, so the baseline of 4 applies; there is nothing for the description to clarify beyond confirming the call requires no inputs.

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 resource and what it returns: per-category price benchmarks with 25th/50th/75th percentile, free share, and median paid price. It does not distinguish itself from siblings like x402_overview or x402_services, so an agent cannot tell from this text alone which to call.

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 audience framing ('For sellers setting prices and buyers checking value') implies when the tool is useful, but there is no explicit when-to-use versus alternatives, no mention of x402_overview/x402_services, and no note on whether data is cached or how often to refresh.

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