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

With readOnlyHint=true already supplied, the description still adds substantive behavior: the output is one call or an atomic batch of decodable steps, and the operation leaves votes, stake amounts, lock ends, and NFT ownership untouched. That last clause is the key assurance an agent needs before sequencing this ahead of other ve(3,3) actions. It does not cover signing/execution flow or failure modes, keeping it short of a 5.

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, no waste, and the core action is front-loaded before the safety note. Both sentences carry information an agent would otherwise have to guess at.

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 and the input schema is well annotated, so the description does not need to explain return values or field formats. What remains thin is the routing between this and the claim-all sibling, which matters given ~90 similarly named prepare_* tools. Otherwise the definition is sufficient to call correctly.

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 80%, so the schema already carries most parameter meaning, including the non-obvious note that chain_id must come from get_ve33_allocations rather than the wallet's chain. The description only maps loosely onto parameters via 'one or more ve-tokens'; it says nothing about claims entries, recipient, or sender. 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?

The description gives a specific verb and resource: 'Generate one call, or an atomic batch of decodable VeToken steps, claiming voter fees from one or more ve-tokens.' The 'one or more ve-tokens' phrasing implicitly separates it from the all-in-one sibling prepare_ve33_claim_all_fees, but that sibling is never named, so the differentiation is left to inference.

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?

It offers one real usage cue — 'always safe to run before any other ve(3,3) action' — which tells the agent this is a low-risk predecessor step. It never states when to pick this over prepare_ve33_claim_all_fees, prepare_rewards_claim, or prepare_lp_position_earnings_claim, and gives no prerequisite or exclusion guidance beyond safety.

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