n8n_create_workflow_from_template

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, but it only states creation and automatic template selection. It does not mention activation defaults, error/fallback behavior if no template matches, side effects, or whether the workflow is created inactive.

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 short sentences with no filler. It front-loads the core action and uses the second sentence to add a key behavioral detail, so every word earns its place.

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 creating tool with no annotations and no output schema, this description is incomplete. It does not state what is returned, what happens when neither templateId nor userRequest is provided, how conflicts are resolved, or which sibling tools should be used to discover templates first.

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 all four parameters are already well documented. The description adds a small amount of context about automatically selecting the best template when templateId is not provided, but it does not add meaningful detail beyond the schema.

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 action ('Create a new workflow in n8n') and the resource ('based on a template'), and it adds the distinguishing auto-selection behavior. However, it does not explicitly differentiate this from sibling tools like n8n_create_workflow or n8n_import_public_template.

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 explicit guidance on when to use this tool versus alternatives, nor any exclusions or prerequisites. The template-based creation use case is implied, but the description leaves the agent to infer when this is preferable to n8n_create_workflow or n8n_import_public_template.

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