Update one workflow node

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

Annotations already mark the tool as destructive (destructiveHint=true). The description adds valuable behavioral context by revealing the non-atomic update risk and the need to acknowledge it, which goes beyond the annotation. No contradiction with annotations.

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 consists of two concise, front-loaded sentences. The first states the core purpose, and the second adds a critical caveat. Every sentence earns its place with no redundancy or fluff.

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?

With six required parameters and no schema descriptions, the description should provide more context about success/failure behavior, side effects, or return value details. It is too brief for a tool of this complexity, even with an output schema present.

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 input schema has zero description coverage (0%), and the description provides no detailed explanation of individual parameters like path, value, or expectedVersionId. While some parameter names are self-explanatory, the description fails to compensate for the schema gap.

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 clearly states 'Update one validated node property while preserving the rest of the workflow.' It specifies the verb ('Update'), the resource ('one validated node property'), and the scope ('preserving the rest of the workflow'), making it distinct from sibling tools like n8n_workflows_delete or n8n_workflows_diff.

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 context by noting the lack of atomic compare-and-swap in the Public API and requiring explicit non-atomic risk acknowledgement. However, it does not explicitly state when not to use this tool or mention alternative tools.

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