Remove reaction

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

The description adds behavioral context beyond annotations by explaining the permission requirement for removing another user's reaction and the default behavior. No contradiction with annotations (readOnlyHint=false, destructiveHint=false) is present.

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 a single concise sentence that is front-loaded with the action and resource, and immediately clarifies the default vs. permission case. No unnecessary words.

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 simple mutation tool with no output schema, the description adequately covers purpose, parameter roles, and permission nuance. It could mention error cases or rate limits, but is sufficiently complete given the low complexity.

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?

With 60% schema description coverage, the description adds value by explaining that 'user' is optional and defaults to the bot's own. However, it does not elaborate on the format of 'emoji' or 'message_id', leaving some gaps. Baseline of 3 is appropriate.

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' and the resource 'reaction', and distinguishes between removing the bot's own reaction (default) vs. another user's reaction (with Manage Messages permission). This is specific and informative.

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 usage context by specifying when to use the tool with different parameters (default bot vs. other user) and the required permission for the latter. It does not mention alternatives like clear_reactions, but the context is clear enough.

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