list_merge_request_emoji_reactions

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

The description states it is read-only and covers common error cases (missing resources, invalid identifiers, insufficient permission, rate limits). It does not detail the response structure, but this is less critical given its read-only nature.

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 concise and well-structured, with no redundant filler. It includes necessary usage and behavioral notes, though some phrases like 'use required identifiers and pagination fields exactly as documented' are slightly generic.

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 description covers purpose, usage, and error handling. It does not explicitly mention the response type (list of emoji reactions), but given the absence of an output schema and the simplicity of the tool, it is reasonably complete for an agent to use correctly.

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 description adds guidance on the format for project_id (numeric ID or URL-encoded path) and mentions pagination, but it also references 'group_id' which is not a parameter of this tool, potentially causing confusion. It does not significantly clarify parameter semantics beyond the schema.

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 tool lists all emoji reactions on a merge request and distinguishes it from a get tool for a single resource, making its purpose unambiguous.

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?

It explicitly advises using this tool for collections and points to the corresponding get tool for single resources. It also mentions pagination fields, providing clear usage guidance.

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