n8n_update_workflow_partial

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

With no annotations, the description carries the behavioral burden. It usefully discloses the fetch-apply-save sequence and that edits are surgical, but it does not mention failure behavior, concurrency/overwrite risks, or whether the change is atomic.

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, no filler. The core intent is front-loaded, the operation list is compact, and the fetch-apply-save behavior earns its place.

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 adequate for selecting the tool but not fully complete for invoking it correctly. It does not explain which parameters apply to which operations, and there is no output schema or return-value note, leaving room for agent uncertainty.

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%, so the schema already documents the parameters. The description adds the operation vocabulary but not per-operation field requirements or semantics beyond what the schema provides.

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: 'Apply surgical edits to an existing workflow without rewriting it.' It also enumerates the exact operations, distinguishing this tool from the full-rewrite sibling n8n_update_workflow.

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 phrase 'without rewriting it' clearly signals use for targeted modifications rather than full replacement, and the operation list shows what kind of edits are supported. It does not explicitly name the alternative or exclusion conditions, but the contrast with full updates is strongly implied.

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