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

Annotations already cover readOnly/idempotent/non-destructive, yet the description adds real value by naming two data traps: mid-epoch partial weights inflating share percentages, and gauges reading zero while votes sit on chain, plus the convention that shares use the last completed epoch. The closing 'free, keyless' sentence duplicates the annotations and slightly dilutes the signal.

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 traps are front-loaded and earned, but the final two clauses ('Free, keyless, read-only. Cost and signer: free and keyless, nothing to sign.') restate the same fact twice and are already covered by annotations, which is wasted space.

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 need not explain return fields, and it correctly focuses on interpretation pitfalls an agent needs before trusting the numbers. Complete for its purpose, though a hint on epoch boundaries relative to the emission rate would round it out.

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 schema already documents the optional address and the omit-to-follow-own-position behavior verbatim. The description adds no syntax or format guidance beyond that, so 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: reading a wallet's gauge-vote allocation from VoterV5, plus epoch status and live emission rate. An agent knows exactly what it gets. It does not explicitly distinguish itself from siblings like my_votes or hydrex_position, which keeps it off a 5.

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?

The description explains the one parameter's behavior (omitting the address follows our own position), which implies a default use case, but it never says when to prefer this over hydrex_position, my_votes, or hydrex_claimable. Usage is inferred rather than stated.

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