list_issue_emoji_reactions

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

The description adds error semantics (missing resources, invalid identifiers, insufficient permission, rate limits) and emphasizes read-only behavior, which goes beyond the annotations. It does not describe the response structure, but that might not be critical for a list endpoint and the description sufficiently conveys the tool's non-mutating 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 front-loads the main action, then provides usage context, error behavior, and parameter details in a logical order. It is not overly verbose, though it could be tightened by removing the conditional `group_id` reference.

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?

For a simple list operation with two parameters and no output schema, the description covers purpose, usage, errors, and parameter format. It doesn't detail return values, but given the simplicity and that the tool name implies a list, it is sufficiently complete for an agent to call it 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 schema covers 100% of parameters, so the baseline is 3. The description adds value by explaining the format for identifiers ('numeric ID or complete URL-encoded path') and mentioning pagination fields. However, it references `group_id` which is not in the schema, potentially causing slight confusion, hence not a 5.

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 uses a specific verb ('List') and resource ('emoji reactions on an issue'), clearly stating what the tool does. It also differentiates from sibling get tools by explicitly saying to use the collection tool for a list and the get tool for a known single resource, which aligns with the sibling list and helps avoid confusion.

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 gives explicit guidance: 'Use this for a collection of resources; choose the corresponding get tool when you already know the single resource to inspect.' This clearly communicates when to use this tool vs. alternatives, which are the get tools among the siblings.

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