n8n_update_workflow

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It explicitly reveals a nontrivial behavior: the tool fetches the current workflow and merges it automatically, which means omitted fields are preserved. This meaningfully exceeds what the tool name alone conveys, though it does not mention possible side effects, permissions, or failure modes.

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 is exactly two sentences with no filler. The main action is front-loaded, and the second sentence earns its place by explaining the critical partial-update behavior. Nothing extraneous is included.

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 a straightforward update operation, and the schema covers all parameters. However, the close sibling n8n_update_workflow_partial creates ambiguity that the description does not resolve, and with no output schema or annotations, the agent still lacks clarity on return values and operational caveats.

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 baseline is 3. The description adds beyond the schema by explaining the semantics of omitting optional parameters: they keep their current values due to automatic fetch-and-merge. This is valuable parameter context that the schema's field descriptions do not provide.

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 clear verb and resource: 'Update an existing workflow.' It clearly identifies what the tool does, but it does not distinguish itself from the similarly named sibling n8n_update_workflow_partial, especially since the description itself claims 'Supports partial updates,' which could blur the line between the two tools.

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 partial-update behavior ('omitted fields keep their current values') implies when this tool is useful, but there is no explicit guidance about when to use this tool versus alternatives like n8n_update_workflow_partial or n8n_create_workflow. No exclusions or alternative routing are provided.

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