n8n_create_workflow

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. It successfully communicates the default inactive state (important for workflow lifecycle management) and optional parameter handling, but omits mutation safety details, error behaviors, idempotency, or permission requirements expected for a creation tool.

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 appropriately brief at three sentences and front-loads the core purpose. The '[UNIFIED]' prefix is unnecessary noise, but the remaining content efficiently conveys essential information without redundancy. Each functional sentence 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 high complexity (6 parameters with nested objects), zero schema coverage, no annotations, and no output schema, the description is insufficient. It fails to explain the return value, the structure of required JSON parameters (nodes/connections), or the semantics of the 'site' parameter, leaving significant operational 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?

Given 0% schema description coverage across 6 parameters, the description fails to compensate adequately. It only mentions 2 parameters (settings, static_data) to note they are optional, leaving critical parameters like 'site', 'nodes', and 'connections' completely undocumented. No guidance is provided on expected JSON structure for the complex node/connection objects.

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 core action ('Create a new workflow') and method ('from JSON definition'), providing specific verb and resource identification. However, it does not differentiate from the sibling tool 'n8n_import_workflow', which may also involve JSON, leaving ambiguity about when to use creation versus import.

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?

The description provides one critical usage constraint ('Workflow will be inactive by default') and notes that 'settings and static_data are OPTIONAL'. However, it lacks explicit guidance on when to choose this tool over 'n8n_import_workflow' or prerequisites for the JSON structure, falling short of explicit when-to-use guidance.

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