n8n_autofix_workflow

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

Annotations show idempotentHint=true and destructiveHint=false. The description adds context beyond annotations by explaining the default preview behavior ('applyFixes: false') and listing specific fix types, clarifying the tool's safe and repeatable nature.

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 a single sentence that packs many details, making it somewhat dense. It could be better structured with bullet points or separate sentences for readability, but it remains fairly concise.

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?

No output schema exists, but the description does not explain what the tool returns (e.g., preview results or confirmation after applying). The 'confidenceThreshold' parameter is mentioned but not elaborated. This leaves gaps in understanding the tool's full behavior.

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 all parameters described in the input schema. The description reiterates the fix categories but does not add substantive new meaning beyond the schema, achieving the baseline score.

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 'Automatically fix common workflow validation errors' and enumerates specific fix categories, distinguishing it from sibling tools like 'validate_workflow' that only check for errors.

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 mentions 'Preview fixes or apply them' and notes the default preview mode, but does not explicitly guide when to use this tool versus alternatives like n8n_validate_workflow or n8n_test_workflow, leaving usage context implied.

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