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

Goes well beyond annotations: it discloses that the output is unsigned transactions in order plus an EIP-5792 batch, that they are simulated from the wallet, that a sign_url is provided for a human owner, and that nothing is broadcast. The 'nothing is sent' framing also reconciles readOnlyHint=true with a builder tool, so there is no annotation contradiction.

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 dense sentences with zero filler, front-loading the action and mode choice, then the return shape, then the safety guarantee. Every clause carries information.

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 no output schema, the description carries the burden of describing returns and does so (ordered unsigned txs, batch form, simulated, sign_url). An agent has everything needed to invoke and to explain the result to the user.

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%, so the schema already documents all four parameters including defaults and enums. The description only restates the receive default (USDC swapped vs AERO) and adds no syntax or format detail beyond the schema; 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 AERO rewards for a position — and immediately names the two output modes (USDC via swap, default, vs AERO). This is clearly distinguishable from siblings such as build_vault_deposit, build_vault_withdraw, or build_vault_move, which involve principal rather than rewards.

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?

Implies context ('The position keeps earning', default receive mode) but never states when to choose this over alternatives like build_vault_withdraw or build_vault_move, nor any prerequisites. Usage is inferable but not spelled out.

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