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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the safety profile is covered. The description adds only the emoji naming convention; it says nothing about channel membership requirements, whether reactions can be removed, or rate limiting, so it provides modest extra context.

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?

One tight sentence, front-loaded with the verb and including a concrete example inline. Nothing extraneous and nothing buried.

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 action tool with no output schema and full annotation coverage, this is close but leaves real gaps: the required 'ts' parameter's format is unexplained and 'team_id' is entirely undocumented. An agent could still call it, but might guess wrong on the timestamp.

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 50%: emoji and ts are described (the description usefully reinforces emoji with examples like 'eyes'), but channel_id and team_id have no description at all. Critically, 'ts' is only glossed as "The message's ts" and the description does not clarify the Slack timestamp format, so the coverage gap is not compensated.

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?

A specific verb ('Add') plus resource ('emoji reaction to a Slack message') makes the operation unmistakable and naturally distinct from siblings like send_slack_message or draft_slack_message. It stops short of explicitly contrasting itself with any sibling, so it lands just below the top mark.

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?

There is no guidance on when to use this versus send_slack_message/draft_slack_message, or on prerequisites (must the bot be in the channel? must the message exist?). The agent must infer all of that from the tool name alone.

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