Delete Merge Request Emoji Reaction

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

Adds value beyond annotations by describing the action as 'permanently' and 'irreversible', aligning with destructiveHint=true. No contradiction; annotations already flag destructiveness. Does not detail permissions or side effects, but the core behavioral trait is covered.

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 sentences, directly stating purpose and a usage hint. No redundant words, well-structured and easy to parse.

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?

Adequate for a simple destructive tool but missing explanation of project_id and potential error conditions. Given no output schema and open world hint, more context on required parameters would improve completeness.

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 only mentions merge_request_iid and award_id as required, but omits project_id entirely. It gives no explanation of parameter roles or formats beyond naming. The pre-check recommendation adds slight context for award_id, but incomplete.

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 it deletes an emoji reaction from a merge request permanently, using verb 'delete' and specific resource 'emoji reaction from a merge request'. It distinguishes from siblings by specifying merge request, avoiding confusion with issue or work item emoji deletions.

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?

Provides a recommended pre-check using gitlab_list_merge_request_emoji_reactions to obtain the award_id. Gives context for prerequisite data. 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.