n8n_update_workflow

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

No annotations are provided, so the description must fully disclose behavior. 'Update' indicates mutation, and 'Send the full updated workflow JSON' suggests a full replacement (PUT-like) operation. However, it does not disclose authentication requirements, idempotency, error handling, or side effects like version increments. Lacks depth for a mutation tool.

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 redundancy: first sentence states purpose, second adds a critical usage constraint. Every word earns its place. Neither too short to be vague nor too long.

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 the description should explain the return value (e.g., updated workflow object, confirmation message). It also omits behavioral details like whether the update merges or replaces fields. Given complexity of an update operation, more context is needed for complete understanding.

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% for all 3 parameters, providing clear descriptions. The description adds the constraint 'full updated workflow JSON', which reinforces the schema's description of workflow_json but does not add new semantic meaning beyond what the schema already 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?

Clearly states 'Update an existing n8n workflow' with specific verb and resource. Distinguishes from create, delete, and activate tools among siblings. The phrase 'Send the full updated workflow JSON' reinforces the nature of the update (full replacement), though it could be more explicit.

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?

No guidance on when to use this tool vs siblings like n8n_create_workflow or n8n_activate_workflow. No prerequisites mentioned (e.g., workflow must exist, need to retrieve current version first). Usage is implied but not explicitly stated.

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