upsert_reaction

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

With no annotations, the description carries full burden. It does add genuine behavioral context: matching criteria, append fallback, NODE navigation support, and the re-normalization/round-trip behavior. But it omits error behavior, permission/auth needs, and what a failed match or invalid reaction produces.

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?

Three sentences, front-loaded with the core upsert behavior, then supporting details. Dense and largely waste-free, though the final clause about the strict setter schema is somewhat implementation-flavored jargon.

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 annotations, no output schema, 0% parameter coverage, and a nested match object demand more from the description. It explains mutation behavior well but leaves the reaction payload, required nodeId, and return/error outcomes undefined.

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 0%, so the description is the only source of parameter meaning. Its '(by trigger/action/destination)' phrase maps usefully to the match subfields (triggerType, actionType, destinationId), but the required nodeId and the untyped 'reaction' object are never explained, leaving the most important payload parameter undocumented.

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+resource with clear semantics: 'Replace the first matching reaction ... or append if none match.' An agent immediately understands this is an upsert. However, it does not name which siblings (set_reactions, clear_reactions, get_reactions) it competes with, leaving that differentiation implicit.

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 replace-or-append framing hints at when the tool is appropriate, but there is no explicit when-to-use guidance versus set_reactions or get_reactions, and no conditions or exclusions are stated. Usage must be inferred entirely.

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