create_issue_emoji_reaction

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

The description only states it adds an emoji, which is a mutation. With openWorldHint: true, the description should disclose side effects (e.g., whether duplicates are allowed, visibility constraints). No such context is provided.

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?

A single, well-structured sentence that includes examples. No unnecessary words. Front-loaded with the action and resource.

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 parameter list (3 required strings) with no output schema, the description provides the essential purpose. Minor omissions like duplicate handling or error cases are acceptable given the tool's simplicity.

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 three parameters have detailed descriptions in the schema (100% coverage). The description adds example emojis but essentially duplicates the schema's 'name' parameter description. Baseline 3 is appropriate.

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 ('Add'), the resource ('emoji reaction'), and the target ('to an issue'), with concrete examples (thumbsup, rocket, eyes). It effectively distinguishes from sibling tools like create_issue_note_emoji_reaction which target notes.

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?

No guidance is provided on when to use this tool versus alternatives such as create_issue_note_emoji_reaction or delete_issue_emoji_reaction. There is no mention of prerequisites, conditions, or context.

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