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

The description explicitly calls the operation an 'idempotent toggle', while the annotations set idempotentHint=false. That is a direct contradiction, and the description also does not reconcile destructiveHint=true, leaving the agent with conflicting safety and idempotency signals.

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 tight sentences front-load the action and toggle rule, followed by a useful API-key scope note. There is no wasted framing or repetition.

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?

Covers the core toggle behavior and emoji/auth scope, but leaves return behavior unspecified despite there being no output schema. It also does not address the destructiveHint=true annotation, which matters for an agent invoking a mutation.

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 already 75%, and the schema documents account and workspace well. The description adds meaningful emoji semantics beyond the schema by explaining that null or omitted means plain upvote and that repeating the same emoji removes the vote.

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 ('Toggle') and resource ('vote or emoji reaction on a feature request'), and the plain-upvote distinction makes the scope concrete. It does not explicitly differentiate from nearby toggle-style siblings such as fr_toggle_bug_affected, so it falls short of a 5.

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?

Explains how to register a plain upvote (omit emoji or pass null) and that calling again with the same emoji removes the vote. This gives clear invocation context, but it does not name alternatives or state when not to use this tool.

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