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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description still adds meaningful context: the calldata is explicitly unsigned, it discloses the exact contract and pool identifiers, it warns that quotes come with a plain risk warning, and it states ANANSI is not an investment. Missing is anything about rate limits or quote freshness/expiry, which matters for a 'live' quote.

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?

It is front-loaded well, opening with 'Live, read-only swap quotes + unsigned ... calldata', but the remainder is one sprawling comma-chained sentence mixing token addresses, pool IDs, quote tiers, return contents and disclaimers. Since no output schema exists, enumerating the return payload earns its place, but 'utility notes' and 'Uniswap swap/pool links' could be tightened considerably.

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 and only zero-required parameters, the description carries the return-shape burden and does list what comes back (quotes, calldata, pool liquidity, links, risk warning). All three optional parameters are covered by the schema. It would be stronger with quote validity/expiry or a note on what happens if liquidity is insufficient.

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 the schema already documents recipient, usd_amount and slippage_bps in detail. The description only echoes usd_amount and recipient while silently omitting slippage_bps. With the schema doing all the work, baseline 3 is correct; the description adds the useful fact that custom amounts override the preset tiers.

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 first clause names a specific verb and resource: live read-only swap quotes plus unsigned SwapRouter02 exactInputSingle calldata for the named ANANSI token/pool. That is far beyond a tautology and tells the agent this is a quote-building tool, not a trade executor. It stops short of 5 because the implicit alternative (topup_quote, buying credits with USDC) is alluded to but never named as a distinct tool.

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?

Usage is implied rather than stated: the tool emits unsigned calldata, so an agent can infer it precedes a swap, and the $0.50/$1 'dust' tier hints at minimum sizes. But there is no explicit 'use this when X, use topup_quote when Y' routing, and nothing states that this tool never submits a transaction. The clause 'credits can also be bought with USDC' gestures at an alternative without naming it.

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