n8n_create_workflow

Does 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. It does convey that valid JSON input is a precondition (implied by the validate-first instruction) and names the configurable surface. However, it omits post-creation behavior: whether the workflow starts active or inactive, whether a created workflow object/ID is returned, and any error semantics. Core behavior is clear but creation outcomes are 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?

Three short sentences, front-loaded with the core purpose, with zero filler. The validation-sequencing sentence earns its place by preventing broken submissions, and the specifiable-fields sentence is compact. The description is appropriately sized for the tool's moderate complexity.

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?

The detailed schema covers the nested node structure, and the description covers creation intent plus the search/validate pre-workflow. Missing pieces are what happens on success (returned object/ID) and the default state of a created workflow, both relevant when an agent chains subsequent calls — and there is no output schema to fill that gap. Adequate, but with clear gaps.

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 coverage is 100%, so all four parameters (name, nodes, settings, connections) are already documented in the input schema. The sentence 'You can specify nodes, connections, and settings' largely restates schema properties and adds only marginal emphasis. Per the baseline rule for high schema coverage, a 3 is appropriate.

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 opens with a specific verb+resource ('Create a new workflow in n8n') and expands scope by naming what can be specified (nodes, connections, settings), making clear this is a from-scratch construction rather than a template-based or update operation. However, it doesn't explicitly differentiate from sibling creation paths like n8n_create_workflow_from_template or n8n_import_workflows, so it stops short of full sibling distinction.

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?

Provides explicit sequencing guidance: 'Prefer n8n_search_nodes + n8n_validate_workflow first so the JSON is valid.' This concretely tells the agent which companion tools to run before invoking this one, which is actionable and specific. It does not state exclusion criteria versus alternatives (e.g., when to choose create_workflow_from_template instead), so it lacks the when-not dimension that would earn a 5.

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