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

Annotations declare this is a non-read-only, non-idempotent, non-destructive write, so the safety profile is already covered. The description usefully adds the self-vote prohibition and the phase constraint, but says nothing about auth requirements or what happens on duplicate votes.

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?

A single tight sentence with the action front-loaded and the two constraints (best answer, not your own) appended. No wasted words, though it is arguably too sparse given the tool's constraints.

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, so return values need not be described. However, for a stateful voting write, the description omits eligibility/auth context and any duplication behavior, leaving gaps beyond the small parameter set.

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 100%, so all three parameters (council id, answer_id, optional api_key) are already documented. The description adds no parameter-level detail such as how answer_id relates to the council, so the schema carries the load.

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 (vote) and resource (best answer), and the 'in the voting phase' scope distinguishes it from a generic vote. It does not explicitly differentiate from the sibling vote_law, which targets laws rather than answers, so sibling routing relies on the reader inferring the phase/resource distinction.

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?

'In the voting phase' implies when to use it and '(not your own)' is a real eligibility constraint, but there is no explicit statement of alternatives (e.g. vote_law) or prerequisites such as being a council member. Usage is implied rather than spelled out.

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