n8n_create_workflow

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

No annotations are provided, so the description bears full responsibility for disclosing behavior. It only says 'creates' without detailing side effects, required permissions, idempotency, or error conditions. The tool mutates state, but the description does not warn about potential conflicts or the need for a valid workflow object.

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 one short sentence, which is concise and front-loaded. However, it is under-specified for a tool with nested objects and no annotations, so it is not appropriately sized. It earns its place but leaves too much unsaid.

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 nested workflow object, three parameters, and no output schema or annotations, the description is far too minimal. It does not explain what the returned data looks like, how the workflow object should be structured (beyond a one-line schema note), or any behavioral context needed to use the tool effectively.

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 description adds no parameter meaning. The schema already describes api_key and workflow, but base_url lacks a description, and the description does not clarify it or any parameter relationships. With 67% schema coverage, the description does nothing to compensate for the 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 a specific action ('creates a new workflow') and resource ('n8n'), which distinguishes it from sibling tools like list, get, activate, and deactivate workflows. It is a direct and unambiguous purpose statement.

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 guidance is provided on when to use this tool versus alternatives. The description does not mention checking existing workflows first, prerequisites, or cases where another tool (e.g., get_workflow or list_workflows) would be more appropriate. The implicit 'create' action is the only hint.

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