n8n_generate_workflow

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

The description discloses stateful behavior (proposals, deployment), caching options, and the need for confirm_deploy. It goes beyond annotations by detailing the multi-step interaction and preview mechanism.

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 concise (5 sentences) and front-loads the main purpose. Each sentence adds necessary guidance, with no fluff or repetition.

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?

The description covers the tool's purpose and parameters well but lacks details about output format (e.g., proposal structure, status codes). Since no output schema exists, this gap may hinder agent understanding.

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?

With 100% schema coverage and detailed parameter descriptions, the main description adds minimal extra meaning. It provides overall flow context but reuses information already in the schema.

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 the tool generates n8n workflows from natural language using AI. It distinguishes from siblings like n8n_create_workflow by focusing on AI-driven generation and a two-step proposal/deploy process.

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?

The description explains the usage flow: call with description to get proposals, then deploy with deploy_id or skip_cache. It implies when to use this tool (for AI generation) but does not explicitly exclude alternatives like n8n_create_workflow for structured input.

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