n8n_generate_workflow

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

The description adds behavioral context beyond annotations: it discloses that the tool returns proposals, involves caching (skip_cache), and requires subsequent calls for deployment. There is no contradiction with annotations (readOnlyHint=false, destructiveHint=false). However, it could mention side effects like creating resources in n8n upon deployment.

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 (about 60 words in 4 sentences), well-structured, and front-loaded with the core purpose. Every sentence adds value without repetition, making it easy to scan.

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 generative complexity and lack of output schema, the description covers the essential steps (generate, skip_cache, deploy, confirm_deploy). It does not elaborate on error handling or idempotency, but for a tool with openWorldHint=true and good parameter descriptions, it is reasonably complete.

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 significant meaning beyond the input schema: it explains that skip_cache returns a preview requiring confirm_deploy, and that deploy_id comes from previous proposals. This clarifies the parameter usage and workflow, fully leveraging the 100% schema coverage.

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 an n8n workflow from natural language using AI, which is specific and distinguishes it from sibling tools like n8n_create_workflow (which likely creates from structured data) and templates. It also outlines the multi-step process of proposal generation and deployment, providing a clear understanding of the tool's purpose.

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 provides explicit instructions on when to use each parameter (e.g., call with description for proposals, then use deploy_id or confirm_deploy to deploy). It explains the sequence of calls but does not explicitly contrast with sibling tools or state when not to use this tool. Some guidance on alternatives or exclusions would elevate it to a 5.

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