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

The description adds substantial behavioral context beyond the annotations: it explains the non-custodial model, that CoinFactory returns only aggregator calldata, that the taker wallet signs and broadcasts, and that fees and gas apply. It also discloses that trades are irreversible, which is important safety context even though annotations already mark the tool as read-only and non-destructive.

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 description is front-loaded with the purpose and quote contents, and most sentences earn their place by clarifying fees, custody, and irreversibility. The final 'not financial advice' sentence is boilerplate but does not significantly harm readability.

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?

There is no output schema, so the description usefully lists what the quote includes: the 1% CoinFactory fee, aggregator fees, route, and buy token risk level. Combined with the safety and custody context, this is complete for an agent to call the tool correctly.

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 high at 80%, so the schema already documents most parameter semantics including token identifiers, amount format, slippage, and taker. The description does not add meaning about specific parameters such as slippageBps or taker, so the baseline score of 3 is appropriate.

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: an indicative price quote for swapping one token for another on Base via a DEX aggregator. It distinguishes this from build_swap_transaction by explicitly saying it is read-only and 'builds nothing', letting an agent immediately understand that this tool returns a quote rather than a transaction.

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?

It clearly establishes the read-only quote context and implies use before building a swap transaction, but it does not explicitly name build_swap_transaction or state exactly when to prefer it over that sibling. The condition is clear enough for an agent to infer the correct usage pattern.

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