discord_react

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

With no annotations at all, the description carries the full burden and provides almost nothing: it doesn't mention that this is a write/mutation, that bot permissions and intents are needed, what happens on duplicate reaction, whether reactions can be removed, or any rate limit. Only the bare mutating verb "Add" signals side effects.

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 short, front-loaded sentence with zero filler. It is concise to a fault — the brevity comes at the cost of the missing behavioral and parameter detail rather than from tight editing.

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 4-parameter write tool with no annotations, no output schema, and only one documented parameter, this description is far too thin. An agent cannot reliably construct the emoji argument or know what the call returns from this alone.

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 only 25% — only bot_token is documented, and channel_id/message_id/emoji are bare strings. The description gives no meaning to any of them and in particular omits the critical emoji format question (unicode character vs. custom emoji as name:id).

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?

States a specific verb and resource ("Add a reaction to a Discord message"), which clearly distinguishes it from sibling tools like discord_send and discord_read that do not add reactions. The purpose is unambiguous, though it says nothing about DM vs. guild channel scope.

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?

No guidance on when to use this instead of alternatives, no prerequisites, no exclusions. The agent must infer on its own that this is the endorsement/emoji-acknowledgement operation rather than sending a message.

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