n8n_generate_workflow

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

Annotations are minimal (readOnlyHint=false, destructiveHint=false, idempotentHint=false), so the description carries the behavioral disclosure burden. It explains the multi-step generation process, caching (skip_cache), and deployment. Missing details on what happens on repeated calls with the same description, but overall transparent.

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 four sentences, each adding distinct information. It is front-loaded with the primary purpose. The last sentence about confirm_deploy slightly overlaps with earlier guidance, but overall efficient.

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 tool's complexity (multi-step, caching, deployment), the description covers the essential flow. It mentions return status 'proposals' but does not detail the return format of proposals or previews. Lacking an output schema, this is a minor gap, but still fairly complete for agent use.

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% with clear parameter descriptions. The tool description adds valuable context by explaining the overall workflow and linking parameters (e.g., 'Get proposal IDs from a previous call that returned status proposals'). This goes beyond the schema alone.

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 itself from sibling tools like n8n_create_workflow (direct creation) and n8n_deploy_template by emphasizing the AI-driven proposal and deployment 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?

The description provides explicit guidance on when to use the tool: start with a description to get proposals, then use deploy_id, skip_cache, or confirm_deploy for subsequent calls. It does not mention when not to use this tool, but the context is clear enough for an agent to decide.

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