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

Annotations cover the safety profile (readOnlyHint=false, destructiveHint=false), and the description adds genuinely non-obvious operational context: the tool needs an AI model, lists the fallback sources, and notes generation is non-persisting. It stops short of saying what comes back on failure or whether partial validation failures are returned.

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?

Front-loaded with the core capability and the non-deployment constraint, then the model prerequisite, then per-argument notes. The Args block is slightly redundant with the schema property names but earns its place by adding meaning the schema lacks.

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?

For a two-parameter, non-destructive generation tool with no output schema, the description covers purpose, prerequisites, and non-persistence. The one gap is the return shape — an agent cannot tell whether it receives the workflow JSON, validation warnings, or a preview identifier to pass to save_workflow.

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 0%, so the description carries the burden and does document both parameters: prompt as plain English intent, tools as optional app/integration names with a concrete example (['slack','postgres']). It could still clarify how tools interacts with node discovery, but the essentials are covered.

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?

States a specific verb and resource ('Generate a complete, validated n8n workflow from a natural-language description') and qualifies it with grounding in real node schemas and automatic fixes. It also separates itself from siblings autofix_workflow, validate_workflow and save_workflow by declaring 'Nothing is deployed -- use save_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?

Gives a clear exclusion ('Nothing is deployed') and routes the agent to save_workflow afterwards, plus spells out the three ways the required AI model can be satisfied. It does not say how this differs from get_ai_workflow_patterns or when to regenerate vs. update_workflow_partial, so sibling routing is only partial.

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