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

No annotations are provided, so the description bears the full burden of disclosing behavior. It mentions opening, adjusting, and rebalancing ranges but does not disclose that this likely executes on-chain mutations, potentially requires authentication or wallet signing, may incur gas/fees, or has side effects on existing positions.

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?

The description is a single, concise sentence that front-loads the core purpose. It is slightly padded by 'Allows agents to', but remains efficient and easy to parse.

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?

For a complex DeFi management tool with 8 parameters and no output schema or annotations, the description is too sparse. It omits action-specific prerequisites (e.g., needing an existing tokenId for adjust/collect), return behavior, and on-chain execution implications.

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 0%, and the description does not explain the parameters. It vaguely hints at ranges and actions, but does not clarify token0, token1, tickLower, tickUpper, amount0Desired, amount1Desired, or tokenId. The action enum is in the schema but not semantically elaborated in the 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 names specific actions ('open, adjust, and rebalance') and a specific resource ('concentrated liquidity ranges on Aerodrome Slipstream'). It clearly distinguishes this tool from siblings like aerodrome_swap and get_aerodrome_yields by focusing on liquidity range management rather than swapping or yield lookup.

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 context is implied: an agent would call this when managing concentrated liquidity positions on Aerodrome. However, there is no explicit guidance on when to use this tool versus alternatives such as aerodrome_swap or get_aerodrome_yields, and no exclusion criteria.

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