n8n_create_workflow

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

Annotations already indicate the tool is not read-only and not destructive, and the description adds valuable context: 'Created inactive' and 'Returns workflow with ID'. It does not disclose potential side effects or permission requirements, but the annotations plus these key behaviors provide adequate transparency.

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 concise sentences: the first states the core action, the second lists requirements and key behavior. It is front-loaded and every sentence adds necessary information without redundancy.

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 tool's moderate complexity (nested nodes/connections) and no output schema, the description covers the essential behavior (inactive creation, return with ID) and requirements. The schema fills in parameter details, so the description is adequate for invoking the tool correctly, though it could add more on connection structure or activation steps.

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?

The schema covers all parameters with descriptions, so the baseline is 3. The description only reiterates that name, nodes, and connections are required, and does not add semantic depth beyond the schema. It is not misleading or insufficient, but it adds minimal value.

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 verb 'Create' and the resource 'workflow', distinguishing it from sibling tools like n8n_update_partial_workflow and n8n_delete_workflow. It also specifies the required fields, making the tool's purpose unambiguous.

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 prerequisites but gives no explicit guidance on when to use this tool versus alternatives like n8n_update_full_workflow or n8n_deploy_template. It does not mention when not to use it or how it differs from update/delete operations, leaving usage context largely to inference.

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