n8n_import_workflow

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

With no annotations provided, the description only states that the tool creates a workflow on the server. It does not disclose whether the import is idempotent, what happens if the workflow already exists, or any side effects (e.g., replacing existing workflow? duplicates?). Given the lack of annotations, more behavioral detail would be helpful, but the description is not misleading.

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 two sentences, front-loaded with the primary purpose. Every sentence adds value: first states the action and resource, second clarifies input and server context. No unnecessary words.

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 has a clear input schema (100% coverage) and no output schema, the description adequately explains what the tool does. It does not detail the return value (which is acceptable since no output schema exists), but it could mention whether the imported workflow's ID or status is returned. However, for a simple import tool with three parameters, the description is mostly complete.

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%, so the schema already documents all three parameters. The description adds minimal value beyond what the schema provides, but it does clarify that the tool expects a 'full n8n workflow JSON' and that server_name defaults if omitted. The purpose of the activate parameter is clear from the schema. A score of 4 is appropriate because the schema does the heavy lifting, but the description adds useful context about the JSON being 'full' and the default behavior of server_name.

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 verb ('import') and resource ('workflow JSON onto an n8n server'), and explicitly mentions creating the workflow on the server. It sufficiently distinguishes from sibling tools like n8n_create_workflow (which may imply a different creation method) and n8n_export_workflow (the reverse operation).

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 this tool is used when you have a full n8n workflow JSON and want to create it on the server. However, it does not differentiate from n8n_create_workflow (could be a different import mechanism) or mention when to use the 'activate' parameter. No explicit alternatives or exclusions are given.

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