Create a workflow on a live n8n instance

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

Discloses that read-only fields are stripped before posting and that workflows are created inactive, adding context beyond annotations (readOnlyHint=false, destructiveHint=false). No contradictions.

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?

Three sentences front-loading purpose, then requirements, then behavior and pairing, with 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?

Covers purpose, prerequisites, behavioral nuances, and pairing with sibling tools; output schema exists but description still provides full context for invocation.

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%; description adds context that the parameter is typically the output of workflow.generate and can be an object or string, enhancing schema meaning.

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?

Clear verb+resource: 'create a workflow on a live n8n instance' distinguishes from siblings like workflow.activate and workflow.generate.

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 states required credentials (N8N_API_URL + N8N_API_KEY), notes that workflows are created inactive (use workflow.activate afterward), and pairs with workflow.generate for end-to-end flow.

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