update_reactions

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

No annotations provided. Description indicates destructive overwrite ('replace its reactions array') and mentions fixing variable references. Lacks details on reversibility, errors, or 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?

Two sentences, no wasted words. Front-loaded with action and object.

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?

No output schema, but description provides enough context for a simple update operation. Could mention response or side effects, but not critical.

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 covers all parameters (100%). Description adds value by stating 'Provide the full array' implying complete replacement, not partial update.

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?

Description clearly states it updates Figma prototyping reactions by replacing the array. It mentions using get_reactions first, distinguishing it from sibling that retrieves 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?

Explicitly instructs to use get_reactions first, modify, then pass updated array. Provides workflow but no explicit when-not to use or alternatives besides get_reactions.

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