n8n_create_workflow

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

No annotations provided, so description must carry full burden. Notes that server_name uses default if omitted, and activate is optional. However, lacks details on idempotency, partial failures, or whether nodes must be valid n8n nodes.

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?

Very concise, two sentences. Front-loaded with purpose. Could include a brief note on usage context without adding much length.

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?

No output schema, so description should hint at return value (e.g., 'Returns the created workflow'). Lacks this. Adequate given moderate complexity and sibling tools that cover other operations.

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 baseline is 3. Description adds no extra context beyond schema; doesn't explain relationships between parameters (e.g., connections must reference node names) or constraints on node types.

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?

Clearly states 'Create a new n8n workflow' with the verb 'Create' and resource 'n8n workflow'. Distinguishes from sibling tools like n8n_import_workflow (imports from file) and n8n_update_workflow (modifies existing).

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?

No explicit guidance on when to use this tool versus alternatives like n8n_import_workflow or n8n_update_workflow. The description implies it's for new workflows, but doesn't exclude cases where import might be better.

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