createReaction

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

No annotations are provided, leaving the description to fully disclose behavioral traits. It only says 'Create a reaction' but does not mention whether duplicate reactions are allowed, whether existing reactions are replaced, what happens on error, or any required permissions. For a mutation tool, this is a significant lack of transparency.

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 a single, clear sentence with no redundant words. It is front-loaded with the action and resource, and every word contributes to meaning. This is appropriately concise for a simple tool.

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 mutation tool with no annotations and no output schema, the description is too sparse. It does not explain return value, error behavior, or any side effects. The schema covers parameters, but the overall context is incomplete for an agent to invoke the tool with full understanding.

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% (emoji, refId, refType all have descriptions), so the schema carries the semantic load. The description adds no additional parameter context, but per the rubric a baseline of 3 is appropriate when schema coverage is high.

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 ('Create') and resource ('reaction on an item'), making the tool's purpose clear. Although 'item' is somewhat generic, the input schema's refType parameter clarifies that reactions are attached to items like notes or emails. No sibling tool has the same create action, so further differentiation is unnecessary.

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, such as getReactions for viewing existing reactions. There is no mention of prerequisites, intended use cases, or exclusion of certain scenarios. Users must infer usage from the name alone.

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