Slack MCP Server

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

No annotations are provided, so the description carries the full burden. It states the action ('Add an emoji reaction') but doesn't disclose behavioral traits like whether this requires specific permissions, if there are rate limits, what happens if the reaction already exists, or what the success/error dictionary contains. For a mutation tool with zero annotation coverage, this is a significant gap.

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 well-structured and front-loaded with the core purpose in the first sentence. The Args and Returns sections are clearly labeled, with each parameter explanation being concise and relevant. Every sentence earns its place with no wasted 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?

Given the tool's moderate complexity (3 parameters, mutation operation) and the presence of an output schema (which covers return values), the description is reasonably complete. It explains all parameters well and states the return type. However, for a mutation tool with no annotations, it could benefit from more behavioral context about permissions or error conditions.

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 0%, so the description must compensate. It provides clear semantic explanations for all three parameters: 'channel_id' (ID of channel containing message), 'timestamp' (timestamp of message to react to), and 'emoji' (emoji name without colons with examples). This adds substantial value beyond the bare schema, though it doesn't cover all possible edge cases.

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 specific action ('Add an emoji reaction') and target resource ('to a message'), distinguishing it from sibling tools like 'remove_reaction' (which removes reactions) and 'post_message' (which creates messages). The verb+resource combination is precise and unambiguous.

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 implies usage context through the parameter explanations (e.g., reacting to a specific message in a channel), but doesn't explicitly state when to use this tool versus alternatives like 'remove_reaction' or when not to use it (e.g., if the message doesn't exist). No explicit guidance on prerequisites or alternatives is provided.

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