discord_delete_my_message_reaction

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description adds real value beyond that: it scopes the blast radius to the bot's own reaction, states that other users are unaffected, and names the required bot permissions (View Channel, Read Message History). The closing note about no approval prompt largely restates destructiveHint, so it is slightly redundant.

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?

Front-loaded with the action and scope, then alternatives, then permissions. Mostly zero waste, though the trailing 'without an approval prompt' sentence repeats what destructiveHint already tells the agent.

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?

An output schema exists, so return values need no explanation. For a 3-parameter mutation tool the description covers scope, side effects, permission prerequisites, and sibling alternatives — everything needed to invoke it correctly.

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% and the emoji parameter already documents Unicode, URL-encoded, and custom name:id formats. The description only names 'emoji' and adds no syntax or format detail beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource ('Delete the bot's own reaction for a specific emoji on a message') and immediately bounds the scope ('only removes the bot's reaction'). This is clearly separable from the sibling reactions tools without opening any schema.

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?

Explicitly routes to alternatives with their selecting conditions: discord_delete_user_message_reaction for other users' reactions and discord_add_my_message_reaction for adding. Both the when and the when-not are covered.

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