Delete MR Note Emoji Reaction

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

Annotations indicate destructiveHint=true, and the description adds 'Irreversible for that reaction', aligning with annotations. No contradictions. Additional context about permanence and required IDs is provided.

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: first states purpose and key trait (permanence), second lists requirements and recommendation. No fluff, front-loaded.

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?

No output schema; description does not mention return values, error handling, or permissions. For a destructive 5-parameter tool, it could elaborate on optional params and outcomes. However, it covers core usage with pre-check.

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 description coverage is 0%. The description names three required parameters and hints at their role, but does not describe optional parameters (project_id, discussion_id) or provide detailed format/semantics beyond what the 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 verb 'Delete', the resource 'emoji reaction from a merge request note', and emphasizes permanence. It distinguishes from sibling tools like create or list 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?

Explicitly lists required parameters (merge_request_iid, note_id, award_id) and recommends a pre-check with gitlab_list_merge_request_note_emoji_reactions. Provides clear context for when to use this tool, though does not explicitly state when not to use it.

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