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

The readOnlyHint annotation is present, so the bar is lower, and the description still adds substantive context beyond it: what the caller receives (LP token, not the underlying pair), what is deliberately not performed (AERO claiming), and that remaining earnings are surfaced by a read bundle so they are not abandoned. The one thing left unsaid is that this only prepares a transaction rather than broadcasting it, which is the fact that would fully reconcile the mutation-sounding verb with readOnlyHint.

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?

Two sentences, front-loaded with the action and immediately followed by the two most consequential caveats (LP token not pair, no AERO claim). The final clause is dense with internal jargon ("read bundle") but still earns its place by explaining why rewards are not silently lost.

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?

With an output schema present and full schema coverage, the description only needs to cover action semantics and gotchas, and it does: token type returned, reward non-claiming, and residual earnings visibility. What is missing is the prepare-versus-execute distinction and any approval prerequisite, both relevant given the readOnlyHint annotation.

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 all four parameters are documented in the schema, so the baseline is 3; the description's mention of unstaking LP tokens from a gauge reinforces the semantics of the gauge and amount fields rather than duplicating them. It adds no new syntax or constraints, so it sits at the schema-driven baseline rather than above it.

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 ("Unstake v2 LP tokens from a gauge") and immediately scopes the result ("returns the LP token, not the underlying pair"), which separates it from the liquidity-withdraw sibling. It also carves out the reward side by noting it "does not claim AERO", implicitly distinguishing it from prepare_aerodrome_gauge_claim, though no sibling is named directly.

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 is implied rather than stated: the note that it does not claim AERO hints that a separate claim step exists, and the note that rewards are still reported hints at a follow-up action. There is no explicit when-to-use versus prepare_aerodrome_liquidity_withdraw or prepare_aerodrome_gauge_claim, and no stated prerequisites such as approvals or existing deposits.

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