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

Beyond readOnlyHint=true, the description discloses that the output is one atomic batch of decodable steps carrying ownerOf and voteState validation calldata, and that nothing about votes, stake amounts, lock ends, or NFT ownership changes. This tells the agent both the construction strategy and the exact non-effects, which the annotations alone would not convey; it stops short of describing failure modes when no active votes exist.

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, both front-loaded with the core action and then the scope constraint. Dense terminology ('decodable VeToken steps', 'validation calldata') is efficient rather than padded, though the second sentence's exclusion list is packed into one clause.

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-value explanation is unnecessary, and the description covers discovery scope, atomic batching, validation calldata, and the invariant that no vote/stake/lock/ownership state changes. For a multi-step transaction-preparation tool that is nearly complete; only the empty-result case and the relationship to the singular claim sibling are missing.

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 parameters are already documented, and the description reinforces the discovery scope of 'sender' as the owner whose VeTokens and active votes are enumerated. It adds nothing about chain_id pairing with ve_token or the recipient default, leaving the schema to carry that load, which matches the baseline 3.

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 a specific compound action: discover every active vote on the sender's VeTokens, then generate one atomic batch of decodable steps claiming all indexed pool fees. The 'all/every' scope implicitly contrasts with the singular sibling prepare_ve33_claim_fees, but the sibling is never named, so the agent must infer the distinction from the wording alone.

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 tool applies when the sender wants all fees across every active vote in one shot, and 'Fees only' rules out vote, stake, lock, and ownership changes. However, it never explicitly says when to choose this over prepare_ve33_claim_fees, prepare_ve33_reinvest, or the per-protocol claim tools, nor does it state prerequisites such as needing existing votes.

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