delete_issue_note_emoji_reaction

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

The description aligns with the destructiveHint annotation by stating 'Remove'. It adds little beyond annotations - no mention of irreversibility, authorization, or side effects. With annotations present, the description is adequate but not enriched.

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?

Two sentences only: first states purpose, second gives conditional guidance. No redundant information. Front-loaded with the core action.

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 5-parameter destructive tool with no output schema, the description covers main purpose and one parameter nuance. However, it lacks details on return value, error conditions, or prerequisites. While adequate, it could be more complete.

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 description's added value for parameters is limited. However, it provides crucial context for discussion_id ('Pass discussion_id for discussion thread replies'), which is not clear from the schema alone. This elevates the score above baseline.

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 ('Remove an emoji reaction') and the resource ('issue note'). It distinguishes from sibling tools like create_issue_note_emoji_reaction and list_issue_note_emoji_reactions by focusing on deletion.

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 provides a specific guideline: 'Pass discussion_id for discussion thread replies.' This helps the agent understand when to use that parameter. However, it does not explicitly exclude cases where discussion_id should be omitted, leaving the schema to imply that.

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