n8n_duplicate_workflow

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While 'Create a copy' implies a write operation, the description lacks details on idempotency, error handling (e.g., if the source workflow doesn't exist), whether the new workflow starts active or inactive, or what the return value contains.

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 a single sentence with no redundant phrases, earning high marks for brevity. However, the '[UNIFIED]' prefix appears to be metadata noise rather than descriptive content, slightly detracting from the structure.

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 the lack of annotations, output schema, and zero schema parameter descriptions, the description is insufficient for a 3-parameter tool. It fails to explain the 'site' parameter, return format, or error conditions, leaving significant gaps in contextual understanding.

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%, requiring the description to compensate. It implicitly maps 'existing workflow' to workflow_id and 'new name' to new_name, but provides no explanation for the 'site' parameter, leaving one-third of the required parameters 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 clearly states the action ('Create a copy') and resource ('workflow'), and implies the requirement of an existing workflow via 'existing workflow with a new name'. However, it does not explicitly distinguish from sibling tools like n8n_create_workflow (create from scratch) or n8n_import_workflow (import from file).

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 no guidance on when to use this tool versus alternatives (e.g., create_workflow), nor does it mention prerequisites such as requiring a valid workflow_id or permissions to access the source workflow.

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