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

With no annotations, the description carries the full burden and does well by disclosing the 'indicative' nature, live on-chain reserve sourcing, and the paid two-step workflow. It stops short of explicitly stating read-only behavior or potential error conditions, but the term 'quote' and the workflow imply no trade execution.

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 sentences, each earning its place: the first defines the tool, the second explains the paid workflow, and the third points to an alternative. Information is front-loaded, with no fluff or redundancy.

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?

Although there is no output schema, the description lists the key outputs and fully explains the two-step paid process. It does not describe response structure or failure modes, but for a quote tool with a clear alternative, this is sufficient. Could be slightly more explicit about the exact response format.

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%, so baseline is 3. The description adds meaningful context especially for x_payment, explaining the exact sequence of omitting it to get terms and then including it to settle and get data. This workflow guidance goes beyond the schema's parameter description.

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 clearly states the tool provides an 'Indicative UniswapV2 swap quote from live on-chain reserves' and explicitly lists the outputs: 'amount out, execution price, and price impact'. It also distinguishes from the sibling 'pricing' tool by noting it focuses on a single trade while 'pricing' lists every price at once.

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 description gives explicit when/how to use: 'call without x_payment to receive this call's exact terms... then call again with x_payment'. It also explicitly names the alternative 'The free `pricing` tool lists every price at once', clearly guiding the agent to choose the right tool.

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