poa_vote

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

With no annotations, the description must carry the full behavioral burden. It usefully discloses that the first vote is final and not retried automatically, which signals irreversibility, but it omits permission/auth requirements, what happens on a duplicate vote (error vs. ignored), and whether any state is overwritten.

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 tight sentences with the action stated first and the critical finality constraint second. No filler, though it is short enough that it could have spent a few more words on the parameters.

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?

For a three-parameter mutating tool with no annotations, no output schema, and 0% parameter documentation, the description is too thin. An agent cannot confirm valid choice values, required identifiers, error behavior, or the response shape.

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% for all three required parameters. The description only echoing 'ballot topic' and the notion of a vote leaves choice formats, valid values, and identifier syntax entirely undocumented, so it does not compensate for the coverage gap.

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 ('Cast one vote on a ballot topic'), which is easily separable from siblings like poa_ballots (listing) or poa_grade. It stops short of naming any sibling or contrasting scope, so it is clear but not differentiated.

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 finality rule ('first vote per topic is final') implies the usage context -- vote once, deliberately -- but no alternative tool or condition is named, and the agent is left to infer when voting is appropriate versus reading poa_ballots first.

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