Creates an immutable baseline copy of an existing workflow, preserving its current state for backup, rollback, or safe comparison before making changes.
Duplicates a workflow as immutable baseline
| Name | Required | Description | Default |
|---|---|---|---|
| reason | No | ||
| confirm | No | ||
| workflow_id | Yes |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Immutable baseline' hints that the resulting copy cannot be modified, but the description says nothing about whether this is a mutation of server state, whether it affects the active workflow, what the 'reason' and 'confirm' parameters do, or whether the operation is reversible. Most of the behavioral surface is undisclosed.
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?
It is a single, front-loaded sentence with no filler, which is structurally good. The terseness tips into under-specification rather than true conciseness, so it is only adequate.
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 3-parameter mutation tool with no annotations and no output schema, the description leaves too much unspecified: no return-value expectation, no parameter guidance, and no context on immutability semantics or side effects. It is materially incomplete 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?
Schema description coverage is 0% across 3 parameters, and the description never mentions workflow_id, reason, or confirm. Nothing beyond the parameter names is conveyed — notably the purpose of 'reason' and whether 'confirm' is required for a destructive/irreversible duplication is left entirely unexplained.
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 verb and resource ('Duplicates a workflow'), which distinguishes it from create_workflow and update_workflow_json. However, the qualifying phrase 'as immutable baseline' is ambiguous — it's unclear whether the tool creates a named baseline copy, a backup snapshot, or something else, and no sibling (e.g. list_backups, rollback_workflow) is referenced to disambiguate.
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?
There is no when-to-use guidance, no when-not-to-use guidance, and no mention of alternatives such as create_workflow or the backup/rollback siblings. An agent gets no basis for choosing this tool over creating or exporting a workflow.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.