discord_delete_user_message_reaction

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

Annotations already declare destructiveHint and idempotentHint, so the description's marginal value is the permission list (View Channel, Read Message History, Manage Messages) and the approval-before-execution note, plus the guarantee that only the target user's reaction is removed. That is solid added context, though it doesn't cover rate limits or failure modes.

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 purpose and scoping, then alternatives, then permissions. Four sentences, all functional; the permission recital is the only slightly bulky part but it earns its space for a destructive moderation call.

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 an output schema, full annotation coverage, and 100% schema descriptions, the remaining burden is routing and permission/destructive context, both of which are provided. Nothing needed to invoke it correctly is missing.

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% and every parameter already has a description covering format (emoji encoding, numeric IDs), so the description adds nothing parameter-specific. 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 another user's reaction ... on a message') and immediately scopes it ('only the target user's reaction'), which cleanly separates it from the sibling tools that manage my-own or all-reactions deletions.

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 the agent: use discord_delete_my_message_reaction to drop the bot's own reaction without moderation permissions, and discord_delete_all_message_reactions_by_emoji to clear everyone's reaction for that emoji. When-to-use and alternatives are both spelled out.

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