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

Annotations already declare non-read-only, idempotent, non-destructive behavior, so the safety profile is covered. The description adds the "open idea" scope constraint, which is genuinely beyond the structured data, but says nothing about what is returned or how a missing vote is handled.

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 front-loaded sentence with no filler. Slight ambiguity in "the person's" (assumed to be the authenticated caller) keeps it from a 5.

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, non-destructive mutation with full schema coverage and rich annotations, this is close to sufficient. Only the edge case of removing a non-existent vote is left unaddressed.

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 coverage is 100% with a single idea_id parameter documented with a pattern, so the schema carries the parameter burden. The description adds no format or sourcing detail beyond it; the baseline 3 applies.

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?

"Remove the person's vote from an open idea" names a specific verb (remove) and resource (vote on an idea), which cleanly contrasts with the sibling vote_for_idea. It never names the sibling directly, but the inverse action is unambiguous from the verb alone.

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 "open idea" implies a precondition (only open ideas accept vote removal) but is not spelled out as a rule, and the description does not point to vote_for_idea as the counterpart action or state what happens if no vote exists. Usage is inferable rather than stated.

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