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

Annotations already declare readOnlyHint=false, openWorldHint=true, and idempotentHint=false, covering the mutation and external interaction profile. The description adds protocol and token-pair context but does not go into side effects like token transfers, approvals, or rebalancing mechanics. The description is consistent with annotations; no contradiction.

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?

A single, front-loaded sentence conveys the core purpose without fluff. It mentions the protocol, the specific action set (open/adjust/rebalance), and the token pair, all in under 20 words. No redundancy or unnecessary detail.

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?

The tool is moderately complex with an enum action and two token parameters, and it has an output schema (so return values are covered). The description is adequate for basic invocation but lacks usage guidance and does not mention prerequisites like signer or approval requirements. Given the output schema and annotations cover safety, this is minor but noticeable.

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 all three parameters (action, token0, token1) are already documented. The description does not add parameter-level detail beyond mentioning 'concentrated liquidity ranges' and the token pair, which is marginal. Baseline 3 is appropriate where the schema carries the weight.

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's purpose: opening, adjusting, and rebalancing concentrated liquidity ranges on Aerodrome Slipstream, with a specific token pair. It distinguishes from siblings like aerodrome_swap (swaps) and get_aerodrome_yields (yields) by mentioning CLAMM and liquidity ranges, though it does not explicitly name those alternatives.

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 explicit guidance on when to use this tool versus alternatives. The description only states what it allows, but provides no exclusions, prerequisites, or scenarios where a different tool (e.g., aerodrome_swap) would be more appropriate. The agent must infer usage from the action enum and context.

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