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

With no annotations, the description must carry the behavioral burden, and it does disclose real operational facts: it calls the native public Uniswap HTTP contract, uses the caller's OpenAny gateway credentials, and that charging/authorization are gateway-determined. However, it says nothing about whether the call mutates anything, rate limits, quote expiry, or how routing preferences affect results.

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, front-loaded with the action, and nothing is redundant. The tradeoff is that the brevity comes from boilerplate rather than targeted information.

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?

This is a complex endpoint with a nested body object of roughly twenty properties, cross-field constraints, no output schema, and no annotations. A description this thin leaves an agent without the domain framing (what a quote returns, that a swap must be signed separately, slippage requirements) needed to use it confidently.

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 reported at 100%, so the schema carries parameter documentation and a baseline of 3 applies. The description adds no meaning about the required body fields, the EXACT_INPUT/EXACT_OUTPUT choice, or the oneOf constraint requiring either slippageTolerance or autoSlippage.

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?

"Get a quote" essentially restates the title "Uniswap Get a quote" and the tool name; it adds no distinguishing detail. It does not say what kind of quote (swap route quote for a token pair), nor how it differs from the many sibling uniswap_post_v1_* endpoints such as swap, order, plan, and check_approval.

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?

There is no guidance on when to use this versus uniswap_post_v1_swap or uniswap_post_v1_order, no prerequisites (e.g. that a quote normally precedes a swap), and no exclusions. The only context given concerns gateway credentials, which is not usage guidance.

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