Delete Issue Note Emoji Reaction

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

The description discloses irreversibility ('permanently', 'Irreversible for that reaction'), which adds value beyond the annotations (destructiveHint=true). There is no contradiction with annotations.

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?

Two short, front-loaded sentences with no unnecessary words. Efficiently conveys purpose, irreversibility, and pre-check recommendation.

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 basic deletion action and required parameters, but omits details about optional parameters and error scenarios. For a simple delete with no output schema, 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 description coverage, the description must compensate. It lists required parameters (issue_iid, note_id, award_id) but does not explain their meanings or mention optional parameters (project_id, discussion_id). Partial coverage.

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 an emoji reaction from an issue note permanently') with a specific verb and resource, distinguishing it from sibling delete tools (e.g., gitlab_delete_issue_emoji_reaction).

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 lists required parameters and recommends a pre-check (gitlab_list_issue_note_emoji_reactions), providing clear context. However, it does not explicitly state when not to use this tool or mention alternatives.

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