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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It adds meaningful behavioral context: votes affect the evening review (a persistent effect) and the constraint 'One vote per idea from one address' (limiting repeat voting). It does not mention reversibility, auth, or other side effects, but for a simple vote tool it discloses the most important behavioral traits.

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?

Three concise sentences: the first states the action, the second explains purpose/effect, and the third gives a constraint. Every sentence earns its place, and the key verb–resource pair is front-loaded. There is no redundant or vague language.

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 single-parameter tool with no output schema and no annotations, the description covers purpose, usage context, and a key behavioral constraint. It is sufficient for an agent to decide when and how to invoke it. The only minor gap is not describing what the tool returns (e.g., success confirmation), but that may be unnecessary for a simple vote action.

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?

The input schema description covers the id parameter fully: 'id of the idea you are backing, as returned by list_ideas.' The top-level description adds only the context 'someone else's idea,' which largely restates the schema's 'idea you are backing.' With 100% schema coverage, the baseline is 3 and the description adds minimal additional semantic value.

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, active verb and resource: 'Back someone else's idea with a vote.' It goes on to explain the effect ('Votes lift an idea in the evening review the owner reads') and explicitly contrasts with commenting, which distinguishes it from sibling comment_idea and submit_idea. An agent can immediately understand what this tool does and how it differs from similar tools.

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 phrase 'this is how you say "this one matters" without writing a comment' provides clear context for when to use the tool vs. leaving a comment. It also says 'someone else's idea,' implying this is not for voting on your own submission. However, it does not explicitly name an alternative tool or state a when-not-to-use condition, falling just short of the top tier.

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