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

Annotations already cover the read-only and open-world profile, yet the description adds real value: a hard cost ($0.003 USDC via x402), the payment rail, the pricing methodology (direct USDC pool or via WETH, best fee tier), and the quote unit. Missing only what the returned quote looks like beyond the number.

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, dense with distinct facts (what, methodology, cost), with the core purpose front-loaded and 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 tool with annotations but no output schema, the description covers cost, routing, and quote basis well. It stops short of describing the response shape (fields, decimals, failure on illiquid tokens), which is the one remaining gap.

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 the single 'token' parameter is well documented as 'ERC-20 token contract on Base', matching the description's framing. The '1 whole token' detail clarifies quote normalization rather than adding meaning to the parameter itself, so baseline 3 fits.

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?

Names a specific verb and resource ('executable Uniswap v3 quote for 1 whole token') plus scope ('any Base ERC-20'), which is clearly distinct from sibling metadata tools like base_token or base_contract. An agent can tell exactly what this returns without opening the schema.

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 scope ('any Base ERC-20') implies when the tool applies, and 'No third-party price API' rules out an alternative approach, but there's no explicit routing versus siblings such as base_token or base_contract, and no stated preconditions beyond having a token address.

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