n8n: Transfer workflow to project

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

Annotations already declare destructiveHint=true and idempotentHint=false, so safety is covered; the description usefully adds the auth/access requirements and destination-existence prerequisite. However, it never clarifies the core behavioral question for a transfer: whether the workflow moves (is removed from the source) or is copied, and what happens to its executions, tags, or active state.

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?

Two tight sentences, with the action front-loaded and the prerequisites following. The only waste is the unexplained '[UNIFIED]' tag at the start.

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 three-parameter destructive mutation with no output schema, the definition covers prerequisites but omits the outcome semantics an agent needs before committing: move vs copy, effect on source-project state, and any partial-failure behavior. Adequate, not complete.

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%, so the description must carry parameter meaning and only partly does: 'workflow' maps to workflow_id and 'destination project' to destination_project_id, both by implication only. The 'site' parameter is never mentioned, leaving an agent to guess whether it is an instance URL, host alias, or region selector.

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 names a specific verb ('Transfer') and resource ('a workflow') plus the destination ('a different project'), which is enough to distinguish it from n8n_transfer_credential and from create/duplicate tools. The '[UNIFIED]' prefix is unexplained noise that adds no meaning.

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?

It states two real preconditions: the destination project must exist and the API key must have access to both source and destination, plus an Enterprise/Pro availability note. It never says when to prefer this over duplicating a workflow, nor what happens if preconditions fail.

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