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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the description is not burdened to repeat those. The description adds context about pairing IDs for mutation tools and mentions the removal method, but does not detail side effects like notification changes or permanence beyond the removal option. It adds modest value without contradicting annotations.

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 somewhat long but well-organized, with clear sections for Chat ID and Message ID. It front-loads the purpose and then provides necessary ID-resolution details. Some repetition exists between the description and schema text, but the structure is efficient and scannable.

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 mutation tool with 4 parameters and no output schema, the description covers how to obtain IDs, keep them paired, and what not to pass. It also names the removal alternative. Missing details like error handling or rate limits are not critical for correct invocation. The description is sufficient for an agent to call the tool 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 description coverage is 100%, so the schema already documents each parameter. However, the description adds actionable retrieval guidance (e.g., 'Obtain with: provider list conversations/inbox chats -> chat.id') and warns against passing certain values, which goes beyond the schema's bare 'Exact chat/conversation ID' phrasing. This is meaningful added value.

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 states a specific verb and resource: 'Add an emoji reaction to one exact WhatsApp, Instagram, Telegram or LinkedIn message'. It also names the sibling tool message_remove_reaction for withdrawal, distinguishing this tool from the removal counterpart. No ambiguity about what the tool does.

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 explicitly instructs to resolve chat/message first and keep chat_id + message_id paired, and names message_remove_reaction as the alternative for withdrawal. It also provides clear 'Never pass' guidance for each parameter, giving the agent concrete rules for correct usage.

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