create_merge_request_note_emoji_reaction

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

The description states the action ('add'), implying a write operation. However, it does not disclose side effects (e.g., whether duplicate reactions are allowed, if it replaces existing ones), permissions, rate limits, or the return value. Annotations only include openWorldHint, which does not cover behavioral traits.

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 a single sentence that is concise and front-loaded. It conveys the core action and a key usage condition without wasted words.

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 no output schema, the description does not mention the return value (e.g., the created reaction object). It also lacks details on prerequisites (e.g., note must exist) or behavior in edge cases. The information is minimally adequate for a simple creation tool but could be more complete.

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?

All parameters have schema descriptions (100% coverage). The description adds value by explaining the conditional usage of discussion_id: required for discussion thread replies, omit for top-level notes. This enhances understanding beyond the schema's minimal description.

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 and resource: 'Add an emoji reaction to a merge request note.' Among siblings, it uniquely targets merge request notes (vs. issues or MR-level emoji reactions), and the mention of 'discussion_id' further specifies the context for thread replies.

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 usage hint: 'Pass discussion_id for discussion thread replies.' This guides the agent on when to include that parameter. However, it does not explicitly state when to avoid this tool or describe alternatives like create_issue_note_emoji_reaction.

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