n8n_generate_workflow

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

Discloses caching behavior via skip_cache and deployment steps. Annotations are sparse (no readOnlyHint details), so description adds value. However, it doesn't mention that deployment creates a persistent workflow in n8n, which could be implied.

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-loaded with main action, uses clear sequencing ('Call with... Then call again... Use...'). 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 the main interaction flow well but omits details like error handling or expected response format. Given no output schema, a bit more on return structure would help, but the description is still sufficient for correct 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?

With 100% schema coverage, the description adds significant meaning: explains that description yields proposals, deploy_id deploys specific proposals, skip_cache bypasses cache, and confirm_deploy deploys the last preview. This goes beyond the schema's field descriptions.

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, distinguishing it from siblings like n8n_create_workflow which likely uses structured input. It specifies the AI-powered nature and the multi-step process of proposals and deployment.

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?

Provides explicit usage patterns: initial call with description for proposals, then using deploy_id or skip_cache. Mentions confirm_deploy for deploying previously generated workflows. Missing explicit when-not-to-use or comparison with alternatives.

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