n8n_autofix_workflow

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

No annotations exist, so the description carries the full burden. It discloses that fixes are 'safe mechanical', that preview is the default, and that applying takes a snapshot first, which provides reversibility context. It could mention permission requirements or what happens if the workflow is invalid, but the disclosed behavior is substantial for this tool.

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?

Two compact sentences with no filler. The first sentence front-loads the tool's purpose, and the second covers the crucial default and save behavior. Every phrase earns its place.

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 2-parameter tool with no output schema, the description is mostly complete: it tells the agent what fixes are applied and how the apply flag changes behavior. A minor gap is that it doesn't specify what the preview output contains (e.g., list of changes), but that is not essential for invoking the tool correctly.

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 100% for both parameters, but the description adds practical meaning beyond the schema: it frames id as the target workflow and explains the apply parameter's preview/save effect and snapshot guarantee. This is more than the baseline 3 for full 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 uses a specific verb ('Apply safe mechanical fixes') and names the workflow as the resource, then enumerates the exact fix categories (missing typeVersion, positions, duplicate node names, dangling connections, missing '=' prefixes). This clearly distinguishes it from sibling tools like n8n_validate_workflow or n8n_update_workflow, which validate or update without the same autofix 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 states the default preview behavior and explains when to set apply=true, giving concrete usage context. However, it does not explicitly contrast this tool with alternatives such as n8n_validate_workflow or n8n_update_workflow, leaving the agent to infer that autofix is for mechanical cleanup rather than validation or manual editing.

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