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

Beyond the annotations (destructiveHint=true, idempotentHint=false), the description discloses real behavior: the email side effect is stopped, with a meaningful exception when you filed or commented on the item, and it states the return value (item plus new vote count). It omits what happens when no vote exists, but the added context is substantive.

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?

The core action and side effect are front-loaded, which is good. However, 'Free; needs a key' and 'Needs an API key or a connected account' restate the same requirement in one short paragraph, wasting one of only three sentences.

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 with no output schema, the description covers purpose, auth, side effects, and the return shape. The main remaining gap is error behavior when no upvote exists, which the non-idempotent hint makes relevant.

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% and the single 'id' parameter is fully documented in the schema, including where the id comes from. The description adds no additional meaning about the id, so the baseline of 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?

The description uses a specific verb and resource ('Takes back your upvote on a feature request or issue'), which implicitly and cleanly distinguishes it from the sibling upvote_feedback. An agent can tell exactly what object is being mutated without opening the schema.

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?

Usage is implied by 'takes back your upvote,' but the description never names upvote_feedback as the inverse alternative or states a precondition such as already having voted. It does note the key requirement, which is a useful gate, but there are no explicit when-not conditions.

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