n8n_import_workflows

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

With no annotations provided, the description carries the full behavioral burden. It does disclose a key trait: imported files become new workflows, suggesting non-destructive import rather than overwrite. However, it does not mention permissions, failure behavior, duplicate handling, or whether imported workflows are validated.

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 tightly written sentence with the core action front-loaded. The parenthetical example is useful and does not add bloat. 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?

Given the simplicity of the tool and full schema coverage, the description is adequate for basic invocation. However, because there is no output schema and no annotations, it leaves some operational unknowns unaddressed, such as what the tool returns after import and how conflicts are handled.

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%, so the schema already documents both parameters and their meaning. The description adds slight context by mentioning backups and the import direction, but it does not materially improve parameter understanding beyond 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 a specific verb and resource: importing workflow JSON files from a local directory as new workflows. It also clearly distinguishes this from creating or templating workflows by emphasizing the directory-based, bulk-import nature.

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 gives a clear contextual example (backups from n8n_export_all_workflows) and implies this is the restoration/import path, but it never explicitly states when to prefer this over n8n_create_workflow or template-based import tools. Usage is implied rather than explicitly routed.

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