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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false, so the write/non-destructive profile is covered. The description adds genuinely new behavior: a 409 on closed or declined ideas, a public vote count, and attribution under the person's account with a 'ask before voting' consent requirement. It does not say what the response contains, but no output schema exists so that is a minor gap.

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?

It is short and front-loaded with the action, but the sentence boundary is broken ('...an open idea Upvotes only, while...'), producing a run-on that reads as two thoughts fused without punctuation. Content density is good; the formatting defect costs it.

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 one-parameter mutation tool with full annotation coverage, the description supplies the key missing context: the closed-idea failure mode, the public visibility of votes, and the consent requirement. Only the return value and the undo path via remove_idea_vote are unaddressed, both minor here.

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?

There is a single parameter with 100% schema description coverage, including a format pattern, so the schema carries the load. The description says nothing about idea_id beyond implying the idea must be open, which is the baseline expectation for a well-documented single-param tool.

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 opens with a specific verb+resource ('Add the person's vote to an open idea') and constrains it to upvotes, which implicitly distinguishes it from the sibling remove_idea_vote. It stops short of naming that sibling explicitly, so differentiation relies on the agent inferring the inverse from the verb.

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?

It gives a clear condition for use ('while the idea is open') and an explicit precondition for failure (409 once it shipped or was declined), plus a consent rule ('ask before voting'). It does not point to remove_idea_vote as the undo path, which is the one obvious alternative an agent would want.

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