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

Annotations already establish readOnly, idempotent, openWorld, and non-destructive behavior. The description adds genuinely new context — that this is a paid call ($0.003 USDC) with live data — but says nothing about rate limits, caching, or data staleness, so it is useful without being rich.

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?

One tightly packed sentence that front-loads the core purpose and appends the data sources and cost. Efficient, though the trailing price parenthetical is slightly awkward in an otherwise content-focused sentence.

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?

An output schema exists, so return-shape explanation is unnecessary, and the description still names the returned fields and sources. The main gap is the absence of when-to-use routing among the many Aerodrome and oracle siblings.

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 100%, so the single minTvlUsd filter is fully documented in the schema already. The description adds no extra meaning about thresholds, units, or default behavior, which is the expected baseline when the schema does the work.

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?

States a specific verb and resource ('Fetch live Aerodrome DEX pool yields') and enumerates the returned data (APYs, TVL, pool addresses, DefiLlama UUIDs). Clear on its own, but it never distinguishes itself from closely named siblings like aerodrome_clamm, aerodrome_swap, or aerodrome_veaero.

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?

No indication of when to use this tool versus the other Aerodrome or oracle siblings, and no prerequisites or exclusions are stated. The only operational note is the price, which is a cost signal rather than usage guidance.

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