n8n_update_full_workflow

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

The description adds the requirement for complete nodes and connections, implying an overwrite behavior. Annotations already indicate non-destructive and idempotent, so no contradiction, but the description could further clarify 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, front-loaded with the core purpose and key differentiator. No wasted words.

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, so description should clarify response or behavior. Lacks detail on what happens to omitted optional fields, though the schema partially covers this. Could be more complete for a mutation tool with 6 parameters.

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 100%, baseline 3. The description adds value by explicitly stating that nodes and connections are required for a full update, beyond the schema's 'required' field which only lists id.

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 'Full workflow update' and specifies the required parameters (nodes[] and connections{}), distinguishing it from the sibling n8n_update_partial_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?

Explicitly contrasts with incremental updates via n8n_update_partial_workflow, telling the agent when to use this tool vs alternatives.

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