n8n_import_public_template

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

With no annotations provided, the description carries the burden of behavioral disclosure. It states the main side effect (creating a workflow) and adds a meaningful caveat that credentials must still be attached separately. It does not cover activation or duplicate handling, but the core behavioral traits are clear.

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 concise sentences with no filler. The main action is front-loaded, and the credential caveat is placed as a separate, easily digestible sentence.

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 covers the core import behavior and the credential post-requisite, making it minimally viable. However, with no output schema, no annotations, and two undocumented optional parameters, it leaves the activate flag and workflow naming behavior unexplained.

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 only 33%, so the description needed to explain the remaining parameters. It only reinforces that templateId identifies the template, while activate and workflowName remain semantically unexplained in both the schema and the description.

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 operation: download an official n8n.io template by ID and create it as a workflow in this instance. It distinguishes this from generic workflow creation and read-only template retrieval, though it does not explicitly differentiate it from sibling tools like n8n_create_workflow_from_template.

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 'official n8n.io template' wording implies the intended scope, and the credential note signals a required follow-up step. However, the description does not explicitly say when to choose this tool over alternatives or when not to use it.

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