slack_add_reaction

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

No annotations are provided, so the description must fully convey behavioral traits. It mentions routing and scope (JWT, tenant, company) but does not describe the actual effect (adding a reaction), potential side effects, permission requirements, or whether it is read-only or destructive.

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 brief but includes some redundant or technical details (e.g., the 'Routes through...' line) that are not directly useful for tool selection. It could be more structured and user-focused.

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?

Despite having an output schema (per context signals), the description does not mention return values or link to Slack API documentation. It lacks completeness for a tool that requires specific argument structure to function 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?

The only parameter 'arguments' is a JSON string with no schema description. The description merely restates it as 'JSON string of arguments' without specifying required fields (e.g., channel, timestamp, reaction) or format. With 0% schema coverage, the description fails to compensate.

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 tool name 'slack_add_reaction' clearly indicates adding a reaction in Slack. The description states it is a Slack connector operation, which is sufficient to convey the purpose, though it does not explicitly mention that it adds an emoji reaction to a message.

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 no guidance on when to use this tool versus alternatives like slack_remove_reaction or slack_list_reactions. It does not specify prerequisites or typical use cases.

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