n8n_export_workflow

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

No annotations are provided, so the description carries the burden. It states the tool is read-only (exporting), but does not disclose any error behaviors, authentication requirements, or rate limits. The description is accurate but minimal in disclosing behavioral traits beyond the obvious.

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 concise at two sentences. It front-loads the core purpose and adds a brief statement about the return value. No wasted 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 no output schema, the description does explain return format (JSON, importable workflow definition). But it lacks details like what happens if the workflow ID doesn't exist, or if the server is unreachable. For a simple export tool, it's mostly adequate but not exhaustive.

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. The description does not add additional semantics beyond what the schema provides, so baseline 3 is appropriate.

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 exports a workflow from n8n as JSON, returns the complete workflow definition for import into another instance. It uses specific verb 'Export', specific resource 'workflow', and output format 'JSON', which distinguishes it from siblings like n8n_get_workflow (which likely returns a different representation) and n8n_import_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 implies usage for exporting workflows and mentions the output is intended for import into another n8n instance, but does not explicitly state when to use this tool versus alternatives like n8n_get_workflow, nor does it mention prerequisites or limitations (e.g., needing the server to be connected).

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