n8n: Import workflow

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

Annotations declare destructiveHint=true and idempotentHint=false, yet the description never explains what gets destroyed — e.g. whether importing overwrites an existing workflow with the same ID, whether the imported workflow starts inactive, or whether a failed import leaves partial state behind. For a destructive, non-idempotent mutation the description adds almost no behavioral context beyond restating that it takes JSON.

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?

Two short sentences, front-loaded with the purpose and followed by the sibling comparison; no padding or repetition. The only waste is the unexplained "[UNIFIED]" tag.

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?

For a destructive three-parameter import with a free-form nested object and no output schema, the description omits the payload contract, the role of `site` and `name_override`, whether the created workflow's ID is returned, and overwrite behavior. An agent cannot call this safely from the definition alone.

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 0% and the description compensates for none of it: the required `site` parameter and the optional `name_override` are not mentioned at all, and `workflow_json` is described only as "JSON definition" despite being an open nested object with additionalProperties=true whose expected structure is entirely undocumented.

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 names a specific verb and resource ("Import a workflow from JSON definition") and draws a distinction against the sibling create tool ("Similar to create but accepts full workflow JSON"). The purpose is clear, though the "[UNIFIED]" prefix is unexplained noise and the create-vs-import boundary is only loosely characterized.

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 phrase "Similar to create but accepts full workflow JSON" implies the selection condition: use this when you already have complete workflow JSON rather than building one field by field. However, there is no explicit when-not guidance, no statement about what happens if the JSON references unknown nodes/credentials, and no mention of when to prefer n8n_create_workflow instead.

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