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

With no annotations, the description must disclose behavioral traits, but it only summarizes high-level actions. It does not mention that these are likely on-chain mutating operations requiring signatures and gas, that lock changes may be irreversible, or that claiming bribes moves funds. The parenthetical '($0.01 USDC)' adds irrelevant noise.

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 short and reasonably front-loaded, but the price aside '($0.01 USDC)' is irrelevant and distracts from the operational content. The single-sentence format is acceptable but not tightly structured for swift parsing.

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?

This is a multi-action, likely state-changing tool with five parameters, no output schema, and no annotations. The description does not cover per-action behavior, parameter constraints, prerequisites, or expected results, so an agent cannot reliably invoke it beyond knowing which actions exist.

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%, so the description must compensate, but it does not explain amount units, tokenId semantics, lockDurationWeeks meaning, or poolVoteAddresses format. It only loosely connects the parameters to locking, voting, and bribes, leaving the agent to rely mostly on parameter names and the action enum.

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 identifies the domain (Aerodrome), the asset ($AERO), and three concrete operation classes: locking, epoch gauge voting, and bribe harvesting. This distinguishes it from swap/liquidity/yield sibling tools, though the verb 'automates' is broad and the description does not explicitly name the sibling 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?

There is no explicit guidance about when to use this tool versus aerodrome_swap, aerodrome_clamm, or get_aerodrome_yields. The intended use is only implied by the enumerated operations; no conditions, exclusions, or prerequisites are stated.

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