Create a workflow on a live n8n instance

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

No annotations are provided, so the description carries the burden. It only states 'Create a new workflow' — a mutation — but does not disclose side effects, permission requirements, idempotency, conflict behavior, or output. The validate_workflow suggestion is useful but not about this tool's behavior. Minimal additional context beyond the tool name.

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 short sentences, with the core purpose front-loaded and the validation suggestion as a bonus. No fluff or redundancy; 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?

Given the complexity of a workflow object (nodes, connections, settings) and no output schema, the description is too sparse. It doesn't clarify return values, error handling, or the required structure of 'workflow'. The validate_workflow hint is helpful but doesn't compensate for the overall lack of context for this non-trivial creation tool.

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%, yet the description does not explain the 'workflow' parameter or its structure. It only references 'workflow' as the target, but adds no meaning beyond the schema. The schema itself has some nested descriptions (e.g., node name), but the tool description fails to compensate for the coverage gap.

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 on your connected n8n instance.' It uses a specific verb ('Create') and resource ('workflow'), and the phrase 'new workflow' distinguishes it from update/delete/activate operations among siblings.

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?

It explicitly suggests 'Consider running validate_workflow first,' which is a clear alternative/related action. This gives the agent guidance on workflow validation before creation. It doesn't explicitly state when not to use this tool (e.g., for existing workflows), but the tool name and sibling context (update_workflow) imply this.

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