List issue reactions

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

The readOnlyHint annotation is presentanding the description adds minimal behavioral context (e.g., comments via note_id). No mention of pagination limits, authentication, or side effects, but the tool is read-only. No contradiction with annotations.

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, one short sentence, with a clean JSON schema. No unnecessary prose or repetition.

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?

The context is sufficient for a straightforward listing task but lacks explicit guidance on when to prefer this over other list tools (e.g., merge request reactions) and any behavioral notes like pagination limits. Still, it covers the key use case.

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?

Parameters are generally well defined: project has both id/path with a description, issue_iid has 'Project-scoped internal ID', and note_id is for comments. Pagination params are standard. Could be clearer on defaults, but adequate.

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 action ('List emoji reactions') and the target resource ('on a GitLab issue or one of its comments'). The tool name and title are echoed but also elaborated, making the purpose specific and distinguishable from sibling tools like list_merge_request_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?

The description provides clear context on when to use it (for issue reactions, including comments via note_id), but it does not explicitly mention when not to use it or how to choose between sibling tools. No exclusionary guidance is given.

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