Create Work Item Emoji Reaction

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

The description is minimal beyond what annotations already provide. It confirms a write operation ('Add') but does not clarify idempotency (e.g., duplicate reactions), required permissions, or side effects. Annotations already signal non-readOnly, non-idempotent, non-destructive, so the description adds little behavioral context.

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 very concise (one sentence) and front-loaded with the action and examples. However, it sacrifices necessary detail for brevity, making it merely adequate rather than exemplary.

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?

With three parameters, no output schema, and a single-sentence description, the definition lacks completeness. It does not describe return values, error conditions, or how the tool fits into the workflow of managing work item reactions.

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 coverage is 0%, and the description only indirectly explains one parameter ('name') by providing examples. It does not clarify the 'iid' (work item internal ID) or 'project_id' (optional project scope). The agent cannot infer complete parameter meaning from the description alone.

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 explicitly states the action 'Add an emoji reaction' and the resource 'work item', with concrete examples like 'thumbsup, rocket, or eyes'. It clearly distinguishes from sibling tools for issues, merge requests, notes, etc., as the target is specifically a work item.

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 usage guidance is provided. The description does not indicate when to use this tool versus other emoji reaction creation tools (e.g., for issues or notes), nor does it mention prerequisites, alternative approaches, or when not to use it.

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