List Issue Note Emoji Reactions

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is clear. The description adds that the tool lists reactions on a specific note and that discussion_id is for replies, which provides some behavioral context beyond annotations, but does not cover pagination or other behaviors implied by the page/per_page parameters.

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 extremely concise with two short sentences that convey the core purpose and a key usage nuance. No extraneous information is included.

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 lack of output schema and 0% parameter schema coverage, the description is insufficiently complete. It does not explain return value format, pagination behavior, or the role of optional parameters. A simple list tool with six parameters should provide more guidance.

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?

The input schema has 0% description coverage, so the description must compensate. It only clarifies the purpose of discussion_id ('for discussion replies') and implicitly identifies note_id and issue_iid as required. However, it does not explain page, per_page, or project_id, leaving their semantics unclear.

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 'List emoji reactions on an issue note,' which is a specific verb+resource combination. It distinguishes from sibling tools like gitlab_list_issue_emoji_reactions (which lists reactions on issues, not notes) by specifying 'issue note' and mentioning discussion_id for 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 implicit usage context by mentioning discussion_id for discussion replies, but it does not explicitly state when to use this tool versus alternatives like gitlab_list_issue_emoji_reactions or other note-related emoji list tools. No exclusions or alternative suggestions are given.

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