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

Annotations only declare readOnlyHint=true; the description adds substantive behavior beyond that – the payout address comes from the account argument rather than the sender, and the plan states which, plus the notable edge case that a zero-earned claim succeeds and transfers nothing. It omits gas/approval or execution-flow context, which is reasonable given the plan-producing nature of the tool.

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?

Three short sentences, front-loaded with the action, then the sharpest gotcha (account vs sender), then the empty-claim edge case. No filler or repetition.

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?

Output schema exists, so the plan contents need not be described. The description covers the two non-obvious behaviors an agent could get wrong (payout address and the no-op-with-success case), which is sufficient for a four-parameter prepare tool restricted to a single chain.

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 coverage is 100% and the account parameter already documents the getReward crediting behavior, so the description mostly restates the schema. Its only additional contribution is that 'the plan states which' address is paid, which reframes rather than expands parameter meaning; baseline 3 applies.

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: 'Claim accrued AERO from a gauge,' which is concrete enough for an agent to act on. It does not explicitly distinguish itself from the several claim-shaped siblings (prepare_aerodrome_incentive_claim, prepare_rewards_claim, prepare_merkl_claim), leaving the AERO-from-gauge scope as the only differentiator.

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 by 'claim accrued AERO from a gauge' – you use it when emissions have accrued to a gauge position. There is no explicit when-to-use, no prerequisites (e.g. approvals, veAERO requirements), and no routing to alternative claim tools, so the agent must infer selection.

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