Update a workflow on a live n8n instance (full replace)

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

With no annotations, the description correctly conveys the destructive/replacement nature of the operation by stating it's a full replace. It also warns about the API limitation. However, it does not explicitly mention side effects like whether the workflow's active status or other metadata is preserved, but the 'fetch first' instruction covers the most critical behavioral nuance.

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 two sentences, front-loaded with the core action, and provides the necessary context in a clear, efficient manner. There is no wasted wording, and the key warnings are included without redundancy.

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?

For a mutation tool with a nested workflow object and no output schema, the description is reasonably complete. It explains the update workflow and the full-replace constraint. Missing details like error handling or activation state are secondary, and the instruction to fetch first covers the main context needed for correct invocation.

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?

The schema has 0% coverage, so the description must add meaning. It implies that the 'workflow' parameter should be the full workflow object obtained from n8n_get_workflow, and 'id' is the workflow ID. This gives some semantic context, but it does not explain the structure or required fields beyond what the schema shows. It adds moderate value but not enough to fully compensate for the lack of schema descriptions.

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 action ('Replace a workflow's definition entirely') and specifies the resource (a workflow on a live n8n instance). It also distinguishes itself from partial updates and from sibling operations like create and get by emphasizing 'full replace' and pointing to n8n_get_workflow as a prerequisite.

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 explicitly provides usage guidance: fetch the workflow first with n8n_get_workflow, edit it, then send the whole thing back. It explains why this is necessary (the public API only supports full-workflow PUT), making the usage context clear and preventing misuse of the tool.

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