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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds useful return-content context by naming voter, wallet, choice, and signed text, but does not mention pagination behavior for limit, ordering, or what the trailing ellipsis omits.

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 description is a single sentence with no filler, so it is appropriately sized. However, the trailing ellipsis and parenthetical make it read as incomplete rather than polished, and the most important usage distinction is not front-loaded.

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 should carry more weight in explaining return shape and filtering. It does list key returned fields and the id filter, but omits limit semantics and does not distinguish this listing tool from the related vote-signing 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 description coverage is 0%, so the description must compensate. It explains that id selects one proposal's votes, but it says nothing about limit, its default, or pagination behavior, leaving half the parameters undocumented.

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 identifies a specific resource and scope: wallet-signed Trana votes, with an optional single-proposal variant via id. It lists returned fields (voter, wallet, choice, signed text), which makes the retrieval purpose clear, though it never explicitly says 'list' or names the sibling wallet_vote alternative.

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 parenthetical hints that id narrows results to one proposal, but there is no explicit guidance on when to use this versus wallet_vote, wallet_vote_message, or trana_vote. The agent is left to infer usage conditions from names.

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