n8n_autofix_workflow

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

Annotations already provide safety hints (readOnlyHint=false, destructiveHint=false, idempotentHint=true). The description adds behavioral details about preview mode, fixing logic, and the types of issues addressed, complementing the annotations without contradiction.

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 concise at three sentences, front-loaded with the main purpose, and efficiently lists fix types without repetition or fluff. Every sentence adds value.

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 (5 parameters, no output schema), the description covers the core purpose, modes, and fix categories. However, it lacks specifics about the output format (e.g., what a preview returns) and how confidenceThreshold influences behavior, leaving minor gaps.

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?

All parameters have descriptions in the schema (100% coverage). The description lists fix types but does not add substantial new meaning beyond the schema. The enum values for fixTypes are partially implied but already fully documented in the schema.

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 'Automatically fix common workflow validation errors' and enumerates specific fix types, distinguishing it from sibling tools like validate_workflow (which only validates) and n8n_update_full_workflow (manual updates).

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 indicates two modes: 'Preview fixes or apply them', with applyFixes defaulting to false (preview). This gives clear usage context but does not explicitly state when not to use this tool or compare with alternatives like manual fixes or other automation tools.

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