n8n_export_workflow

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

No annotations provided, so description carries full burden. Discloses output format (JSON) and non-destructive nature via 'export' semantics. Missing details on whether credentials/execution history are included, file size limits, or if operation is rate-limited.

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?

Extremely brief (two sentences). Information density is high despite '[UNIFIED]' tag consuming front-loaded space. No redundancy, though brevity comes at cost of parameter documentation.

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?

Severely incomplete given 0% schema coverage and lack of annotations/output schema. Required parameters 'site' and 'workflow_id' undocumented. No explanation of return value structure or error conditions.

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 0% with zero parameter descriptions. Description fails to compensate: 'site' is ambiguous (URL? Instance name? ID?) and 'workflow_id' lacks format guidance. Critical gap for required parameters with no schema documentation.

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?

States specific action (Export) + resource (workflow) + format (JSON). The use cases (backup/sharing) help distinguish from siblings like n8n_get_workflow or n8n_update_workflow. '[UNIFIED]' prefix is noise but doesn't obscure clarity.

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?

Provides implied usage context via 'backup or sharing' use cases. However, lacks explicit when-to-use guidance (e.g., when to choose export vs get_workflow) and doesn't reference inverse operation n8n_import_workflow.

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