n8n_import_workflow

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It fails to mention whether import creates new workflows or overwrites existing ones, ID generation behavior, validation requirements for the JSON, or side effects. The phrase 'accepts full workflow JSON' is the only behavioral hint.

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 appropriately brief with two efficient sentences. The '[UNIFIED]' prefix appears to be metadata noise but doesn't significantly detract. The content is front-loaded with the core action, though the tag could be removed for cleaner presentation.

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 complex operation like workflow import with nested JSON objects and no output schema or annotations, the description is insufficient. It lacks details on error handling (malformed JSON, missing fields), whether imported workflows are activated by default, credential mapping behavior, or what the tool returns (new workflow ID? full object?).

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?

With 0% schema description coverage, the description inadequately compensates for undocumented parameters. While 'accepts full workflow JSON' hints at the workflow_json parameter's content, it completely omits semantics for 'site' (instance identifier? URL?) and 'name_override' (renaming behavior? optional?), leaving critical parameters unexplained.

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 imports a workflow from JSON definition, providing specific verb and resource. It distinguishes from sibling n8n_create_workflow by noting it 'accepts full workflow JSON,' though it could further differentiate from n8n_update_workflow or n8n_export_workflow.

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 provides implied usage guidance by comparing to create ('Similar to create but accepts full workflow JSON'), suggesting when to use this over n8n_create_workflow. However, it lacks explicit when-not-to-use guidance or prerequisites (e.g., whether the workflow JSON must be exported from the same n8n instance).

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