Create a workflow on a live n8n instance

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

Description adds behavioral detail beyond annotations: strips read-only fields before posting and creates workflows inactive. Annotations only show non-destructive and non-idempotent. No contradiction with annotations (readOnlyHint: false is consistent).

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, each serving a purpose: purpose+prerequisite, behavioral detail, and usage pairing. No wasted words, front-loaded with essential info.

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 single parameter, full schema coverage, and output schema exists, description covers prerequisite, behavioral nuance, post-usage step, and sibling relationship. Sufficient for agent to select and invoke correctly.

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 description coverage is 100%, but description adds value by stating the workflow parameter is 'typically the output of workflow_generate', linking to sibling tool. Also clarifies it can be parsed object or JSON string.

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 'Create a workflow on a live n8n instance' with specific verb and resource. It distinguishes from siblings by mentioning pairing with workflow_generate for 'describe -> deploy'.

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 prerequisites (N8N_API_URL + N8N_API_KEY) and post-usage instruction (call workflow_activate). Pairs with workflow_generate, indicating when to use it in the workflow lifecycle. No explicit when-not-to-use, but context is clear.

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