n8n_update_workflow

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

No annotations are provided, so the description carries full burden. It mentions 'Send the full updated workflow JSON' which hints at a full replacement behavior, but does not disclose whether partial updates are supported, what happens to existing workflow state (destroyed?), or authentication requirements. For a write operation, this is insufficient.

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 very concise: two sentences, no fluff. It front-loads the purpose and adds a key behavioral hint ('full updated'). However, it is slightly under-specified for a mutation tool, preventing a perfect score.

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?

Given the tool's complexity (mutation with 3 parameters) and lack of annotations/output schema, the description is too brief. It does not explain return values, partial updates, or error scenarios. The hint about 'full' is valuable but incomplete.

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 baseline is 3. The description adds no extra information beyond the schema's parameter descriptions. It mentions 'Send the full updated workflow JSON' which aligns with the workflow_json parameter but adds no new semantics.

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 the tool's purpose: 'Update an existing n8n workflow' with the verb 'Update' and the resource 'workflow'. It distinguishes from siblings like n8n_create_workflow and n8n_delete_workflow by specifying 'Update an existing', implying modification. However, it could be slightly more explicit about differentiating from n8n_export_workflow or n8n_import_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 description implies usage for updating workflows but does not explicitly state when to use this tool over alternatives (e.g., n8n_create_workflow for new workflows, n8n_delete_workflow for deletion). No guidance on prerequisites or when not to use it is provided.

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