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

Annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the mutation/irreversibility profile is covered structurally. The description adds one genuinely new behavioral fact, the $0.01 USDC fee per invocation, but omits auth/approval requirements and whether lock actions are reversible.

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 with no wasted words; the core resource and fee are stated immediately. It stops just short of being too terse for the number of sub-actions it bundles.

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 values need not be explained, and annotations carry the safety profile. However, for a multi-action governance tool with destructive effects, the description says nothing about network/chain scope, token approvals, or how the five action values behave differently.

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% and both parameters (action, amount) are documented with an enum for action, so the schema carries the parameter burden. The description only loosely maps its three named flows onto the five enum values and adds no formatting or unit detail beyond what the schema gives.

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 states specific verbs and resources (AERO locking, epoch gauge voting, bribe reward harvesting) scoped to Aerodrome, which clearly separates it from swap/liquidity siblings like aerodrome_clamm and aerodrome_swap. It never explicitly names those siblings or states it is not a swap tool, but the activity described is distinctive enough that an agent can tell it apart.

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 when-to-use or when-not-to-use guidance, no prerequisites, and no named alternatives among the 27 sibling tools. The action enum implies selectable flows, but the description gives no trigger conditions or routing advice.

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