toggle_activity_emoji_reaction

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

Beyond the annotations, the description explains the conditional mutation: it adds the reaction if absent and removes it if present. This usefully clarifies why destructiveHint is true and idempotentHint is false, though it does not mention permission requirements or the preview behavior that is covered by the confirm parameter schema.

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 front-loaded with the exact action, followed by a concise explanation of toggle behavior and the allowed reaction values. Every sentence and the value list add useful information without filler.

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?

The description is largely complete for a three-parameter mutation tool: it covers purpose, toggle behavior, and reaction values, while annotations cover safety and the schema covers confirm preview behavior. The main remaining gap is that activity_id is not explained in either the description or the schema.

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 description compensates for the missing enum on reaction by listing all accepted emoji values. However, activity_id remains undocumented, and confirm is only described in the schema; with 33% schema description coverage, this is adequate but incomplete.

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: 'Toggle an emoji reaction on a work package comment activity.' This clearly identifies the action and target, though it does not explicitly distinguish itself from the read-only sibling list_work_package_reactions.

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 toggle semantics imply when the tool is useful, but the description provides no explicit when-to-use guidance, prerequisites, or comparison to sibling tools such as list_work_package_reactions. The important confirm/preview workflow is only documented in the schema, not in the description.

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