add_comment_reaction

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

Annotations tell the agent this is a non-read-only, non-destructive mutation, but the description adds nothing beyond that. It does not say whether adding a duplicate reaction is idempotent or an error, whether reactions can be removed, who may react, or what happens on success — all meaningful for a mutation tool.

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 single sentence is front-loaded and waste-free, but it is under-specified rather than optimally concise — it omits information that would make the sentence earn more of its place.

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 three-parameter tool with full schema coverage and annotations, the essentials are present across structured fields. Still, the description leaves behavioral questions (idempotency, error on duplicate, return behavior) unanswered, and there is no output schema to compensate.

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 issueId, commentId, and the reaction enum are fully documented in the schema, which sets the baseline at 3. The description contributes no additional parameter meaning (e.g., whether reaction must match the exact enum casing, or that commentId accepts a longId form).

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 a reaction to a comment"), which is unambiguous about the operation. However, it offers no differentiation from related siblings like add_comment or add_entity_comment, so an agent must rely on the name alone to route correctly.

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 when-to-use guidance, no mention of prerequisites (e.g., needing an existing comment), and no routing to alternatives such as add_comment or the entity-comment equivalents. The agent must infer all usage context from the tool name.

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