Create Issue Note Emoji Reaction

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

Annotations indicate readOnlyHint=false (write operation) and idempotentHint=false (not idempotent). The description adds context about discussion_id handling. It does not contradict annotations and provides a behavioral detail beyond what annotations convey.

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 two short sentences with no redundant information. It is front-loaded with the purpose and concise.

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?

Given the tool's complexity (5 parameters, no output schema) and many sibling tools, the description is too minimal. It lacks parameter explanations, usage context, and does not help disambiguate from similar emoji reaction tools.

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%, so the description must compensate. Only discussion_id is explained (for discussion replies). Parameters like name, note_id, issue_iid, and project_id are not described. This is insufficient for understanding parameter semantics.

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 explicitly states the action ('Add an emoji reaction') and the target resource ('an issue note'). It distinguishes from sibling tools like gitlab_create_issue_emoji_reaction (which targets issue, not note) and gitlab_create_merge_request_note_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 provides one usage hint ('Pass discussion_id for discussion replies') but does not offer explicit guidance on when to use this tool versus alternatives (e.g., vs gitlab_create_issue_emoji_reaction). No when-not or exclusion criteria are given.

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