create_issue_emoji_reaction

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

Annotations only include openWorldHint: true, which is sparse. The description compensates by disclosing that it changes remote GitLab state, requires permissions, and returns errors instead of silently applying invalid requests. This adds value beyond annotations. However, it doesn't detail side effects like duplicate reactions or rate limits specifics, but it mentions rate-limit errors. With minimal annotation, 3 is fair.

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 moderately sized but packs useful guidance: usage context, permissions, error behavior, and identifier handling. It front-loads the purpose and usage instruction. Could be slightly more concise but each sentence contributes value.

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 tool complexity (3 params, all required, no output schema), the description covers usage, permissions, error cases, and parameter details. It lacks explicit examples beyond emoji names and doesn't mention pagination (not applicable here). The sibling list shows many similar emoji tools, but the description helps distinguish by saying 'new resource' vs 'update/edit'. Overall complete for safe invocation.

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?

Schema description coverage is 100%, so all three parameters (name, issue_iid, project_id) are documented in the schema. The description adds clarity for name ('e.g. thumbsup') and project_id ('numeric ID or complete URL-encoded path'), but that is already in the schema. It emphasizes providing identifiers as documented, which is marginal. Baseline is 3 because schema does the heavy lifting.

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?

Description clearly states the action: add an emoji reaction to an issue, with verb 'Add' and specific resource 'emoji reaction to an issue'. It explicitly differentiates from siblings by contrasting with 'create' versus 'update/edit' tools, especially emoji-related tools like list_issue_emoji_reactions and delete_issue_emoji_reaction.

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 explicitly says when to use this tool: 'Use this for a new resource or action; choose the corresponding update or edit tool when the resource already exists'. It gives context about permission requirements and error handling, but does not explicitly name sibling alternatives or provide exclusions for other create tools like create_merge_request_emoji_reaction. Still clear enough.

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