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

Adds meaningful behavior beyond the annotations: it resolves from chain so 'a zero here is a real zero rather than a degraded API', it explicitly disclaims building or signing transactions, and it states the tool is free and keyless. These are real operational facts (cost, signer, zero-semantics) not covered by readOnlyHint/idempotentHint.

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?

The opening is strong and front-loaded, but the closing is redundant: 'Free, keyless, read-only. Cost and signer: free and keyless, nothing to sign' says the same thing twice, wasting a sentence in an otherwise tight description.

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, the description needn't explain return values, and it correctly focuses on what the numbers mean (real zeros vs degraded API) and what it does not do (no signing). Complete enough to call correctly, missing only explicit routing to sibling tools.

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 both optional params are documented in the schema, so the baseline is 3. The description reinforces the semantics ('every gauge a wallet votes for' maps to address, 'per veNFT' maps to tokenIds) but adds no format, default, or edge-case detail beyond that.

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 resource and scope: per-gauge fee and bribe contracts, every reward token tracked, and claimable amounts per veNFT, all resolved from chain. It also clarifies the output contract ('claim calldata SHAPES... builds and signs nothing itself'), which separates it from prepare_claim/submit_claim class siblings, though no sibling is named explicitly.

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 framing it as 'the money answer' for a voting wallet, and by noting the caller must build their own transaction. But there is no explicit when-to-use/when-not guidance and no named alternative (e.g. hydrex_votes for vote history, hydrex_position for balances), so the agent must infer the routing.

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