n8n_update_full_workflow

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

Annotations already indicate non-read-only, non-destructive, and idempotent behavior. The description adds the key behavioral trait that this is a full replacement (requires complete nodes/connections). While it could clarify what happens to omitted fields, the current level is sufficient given annotation coverage.

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 with no extraneous information. The first sentence states the core purpose, the second provides critical usage nuance. Highly efficient and front-loaded.

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?

Covers the essential distinction from the sibling tool and the required components. However, it does not discuss return behavior or clarify that nodes/connections are technically optional in the schema but recommended for a full update. Slight gap, but overall adequate given the tool's complexity and absence of output schema.

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% with detailed descriptions for each parameter. The description reiterates that nodes and connections are required for a full update, reinforcing the schema but not adding new semantic information. Baseline of 3 is appropriate.

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 'Full workflow update' and distinguishes itself from the sibling 'n8n_update_partial_workflow' by specifying that it requires complete nodes and connections. The purpose is unambiguous and well-differentiated.

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 states the requirement for complete nodes and connections and directs users to the partial variant for incremental updates. This provides clear when-to-use and when-not-to-use guidance, leveraging the sibling context.

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