create_issue_note_emoji_reaction

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

Annotations provide openWorldHint: true, but the description does not elaborate on behavioral implications like persistence, idempotency, or whether the reaction creation is tracked. It adds context on discussion_id usage, but overall behavioral traits are not fully disclosed beyond the annotation hint.

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 extremely concise: two sentences, each serving a purpose. No redundant or wasted words, and the key information is front-loaded.

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's simplicity (5 parameters, all described in schema, no nested objects), the description adds essential context for the optional parameter. It does not describe the return value, but since there is no output schema, this is acceptable. The combination of schema and description is sufficient for 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 coverage is 100%, so the schema already documents all parameters. The description reinforces the discussion_id usage with a concrete example ('Pass discussion_id for discussion thread replies'), but does not add new meaning beyond the schema's description.

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 an emoji reaction' and the resource 'issue note.' It distinguishes from siblings like create_issue_emoji_reaction (for issues) and create_merge_request_note_emoji_reaction (for MR notes) by specifying 'issue note.' The additional detail about discussion_id for replies adds precision.

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 provides context on when to use discussion_id (for discussion thread replies) but does not explicitly tell when to use this tool over alternatives like create_issue_emoji_reaction or create_merge_request_note_emoji_reaction. The context is clear enough for an informed agent, but lacks explicit exclusions.

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