n8n_create_workflow

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

No annotations provided, so description carries full burden. Discloses that it strips read-only fields (id, active, createdAt, ...) before posting and that workflows are created inactive. Does not cover error handling or rate limits, but adds meaningful behavioral context.

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?

Four succinct sentences, each providing distinct information: purpose and prerequisites, behavioral detail, activation note, and pairing context. No wasted words.

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 no output schema, description lacks explanation of the return value (e.g., created workflow object or confirmation). Also missing error handling or validation details. Behavioral coverage is strong but output context is absent.

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% and description adds value by noting that the workflow JSON is typically the output of n8n_generate_workflow and accepts both object or string forms. Also implies stripping of read-only fields relates to the parameter.

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 workflow on a live n8n instance' with specific verb and resource. Distinguishes from siblings by mentioning pairing with n8n_generate_workflow and n8n_activate_workflow.

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?

Explicitly lists prerequisites (N8N_API_URL + N8N_API_KEY), states that workflows are created inactive and directs to n8n_activate_workflow afterwards, and notes pairing with n8n_generate_workflow for end-to-end usage.

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