n8n_autofix_workflow

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

Annotations indicate non-destructive (destructiveHint false) and idempotent (idempotentHint true). The description reinforces this by offering a preview mode (applyFixes: false) and listing specific fix categories. However, no information on rate limits, auth requirements, or what happens to existing unsaved changes. Still, behavioral context is adequate.

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 (2 sentences), front-loads the main action, and lists specific fix types without unnecessary elaboration. Every word 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?

The description lacks details on return format (preview vs apply outcome). It does not explain if the tool returns a diff or modified workflow. For a tool with no output schema, the description should compensate but fails to. However, given the simplicity of the tool, it is mostly adequate.

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 schema descriptions (100% coverage). The tool description adds value by summarizing the fix categories in a single sentence, providing a quick overview beyond the enum list. This helps an agent understand the scope without parsing 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 uses specific verb 'fix' and resource 'workflow validation errors', listing concrete fix categories (expression format, typeVersion, etc.), clearly distinguishing from sibling tools like validate_workflow (validation only) and update_workflow (manual update).

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 implies usage for fixing validation errors but does not explicitly state when to use this tool versus editing manually (n8n_update_*) or validating first. No guidance on prerequisites or when not to use.

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