Delete Issue Emoji Reaction

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

Annotations already indicate destructiveHint=true. The description adds value by specifying 'Irreversible for that reaction' and implying the need for prior data via pre-check. It does not cover permissions or side effects but exceeds the annotation baseline.

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 three sentences, each with a distinct purpose: purpose, effect, and usage hint. No unnecessary words; front-loaded with the key action.

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?

The description covers the core action and effect but lacks details on optional parameters (project_id), return value, and error conditions. For a simple delete tool, it is adequate but not fully comprehensive.

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?

With 0% schema coverage, the description should compensate but only briefly states 'Requires issue_iid and award_id.' No explanation of what these IDs represent, where to find them, or the optional project_id. This is minimal semantic help for an agent.

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 ('Delete'), the resource ('emoji reaction from an issue'), and emphasizes permanence ('permanently', 'Irreversible'). It distinguishes from sibling tools that delete emoji reactions from merge requests or work items.

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 provides a clear pre-check recommendation ('gitlab_list_issue_emoji_reactions') and notes required parameters. However, it does not explicitly mention when not to use this tool or compare it to alternative delete tools for similar resources.

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