Remove issue reaction

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

Annotations already indicate destructiveHint=true and readOnlyHint=false, and the description consistently states 'Remove', but adds no extra behavioral details beyond the annotation, such as permissions or idempotency implications.

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 description is a single, clear sentence with no unnecessary words, efficiently conveying the essential purpose.

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 simple removal operation, the description is complete enough. It does not explain return values, but this is acceptable given the straightforward nature of the operation and the absence of an explicit output schema.

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 schema has 4 parameters with only 2 described (project and issue_iid) from the JSDoc. The description clarifies 'award_id' as the identifier but leaves 'note_id' unexplained, and does not compensate for the missing parameter descriptions beyond what schema provides.

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 clearly states the action (remove), the resource (emoji reaction), and the context (GitLab issue or issue comment) with the identifier (award ID). It clearly distinguishes from sibling tools like add_issue_reaction and list_issue_reactions.

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 description implies usage when a reaction needs to be removed, but does not explicitly mention when not to use or compare with alternatives. It is straightforward enough for a typical agent to infer the appropriate context.

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