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

Beyond the readOnly/openWorld annotations, the description discloses a concrete cost model ($0.002 USDC per successful call, x402 payment on Base/Solana/Arc) and that failed calls are free — material for an agent deciding whether to call. Return shape is not described, but an output schema exists to cover it.

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?

Three short sentences: resource and scope first, the disambiguating 'no prices' caveat second, cost third. No filler and nothing an agent must wade through before the key framing.

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 parameterless, read-only listings call with an output schema, the description covers what is returned, what is excluded, and the payment requirement. The only gap is pagination — 'limit' implies paging but neither cursors nor truncation behavior is mentioned.

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 coverage is 100% and both parameters already document defaults and ranges (limit 1-200 default 20; quote e.g. USD/EUR/BTC default USD). The description only echoes the quote filter and its default, adding no syntax or semantics beyond the schema, 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?

States a specific verb and resource (Coinbase Exchange trading products/pairs) plus the attributes returned (status, minimum order sizes) and the filter (quote currency). The clause 'Lists what can be traded; no prices' cleanly separates it from price/oracle siblings such as finance_coinbase_orderbook_candles and crypto_coinbase_spot_exchange.

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 'no prices' exclusion tells the agent this is a metadata lookup rather than a quote source, and the default quote currency sets the normal calling mode. It stops short of explicitly naming the alternative tool to use when prices are wanted, leaving that inference to the agent.

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