Comfy swap quote

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

Annotations already declare read-only, idempotent, open-world, and non-destructive behavior. The description adds that it is an eth_call, includes live per-pool fee rates when readable, and returns null for unknown impact or fees, which is useful behavioral context beyond the annotations.

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 brief and front-loaded, with no filler. Return-value and null-handling notes are compactly packed into two sentences.

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?

With no output schema, the description does a decent job of describing key return values and null behavior. However, it leaves gaps around parameter meaning, slippage handling, and how this quote should be used with the swap-building sibling.

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 only 25%, so the description needs to compensate for undocumented parameters. It does not explain token, side, or slippage_bps semantics, and adds little beyond the schema's amount description and the phrase 'exact-input'.

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 technical operation: a read-only exact-input CLQuoter eth_call on 0G mainnet that returns expected and minimum swap output. An agent can identify it as a quote tool, but it does not explicitly distinguish it from the sibling comfy_build_swap_tx.

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?

Read-only and exact-input imply this is a preview/quote step, likely before building a swap transaction, but the description never says when to use it instead of comfy_build_swap_tx or other siblings. Usage is implied rather than stated.

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