create-workflow

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

With no annotations, the description partially discloses behavior: requires clientId from init-n8n (auth dependency) and enforces formatting. However, it does not mention side effects, rate limits, or other operational details. Adequate but not thorough.

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 sentences, each with distinct value: purpose, structural requirement, formatting requirement. No redundant or extraneous text. Highly efficient.

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 4 parameters with nested objects and no output schema, the description covers key usage constraints (empty arrays, compact JSON) and references auth (clientId). Missing explicit return value information, but for a creation tool the return is inferable.

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 covers 100% of parameters. The description adds value beyond schema by specifying that nodes and connections must be provided even if empty, and that the entire payload must be compact single-line JSON. This compensates for any ambiguity in the typical object format.

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 ('workflow'). It effectively distinguishes from sibling tools like deactivate-workflow or test-workflow by its explicit creation verb.

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 essential usage constraints: must supply full workflow structure with nodes and connections arrays (even if empty), and arguments must be compact single-line JSON. Lacks explicit when-to-use vs alternatives, but constraints are clear and useful.

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