n8n_transfer_credential

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

With no annotations provided, the description carries the full burden. It successfully discloses the authentication/licensing requirement (Enterprise/Pro), but fails to clarify whether the transfer is destructive (moves vs. copies the credential), potential side effects, or rate limiting concerns.

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 appropriately concise and front-loaded with the essential action and constraint. The '[UNIFIED]' and '[Enterprise]' metadata tags add minor noise but do not significantly impede clarity.

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 credential transfer operation with 0% schema coverage and no annotations, the description is incomplete. It omits critical details about parameter semantics, the fate of the source credential post-transfer, and expected return values or success indicators.

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?

Given 0% schema description coverage, the description inadequately compensates for the three undocumented parameters. While 'to another project' hints at destination_project_id, it provides no guidance on what 'site' refers to (URL, instance name, etc.) or the expected format for credential_id.

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 specific action ('Transfer'), resource ('credential'), and scope ('to another project'), effectively distinguishing it from sibling tools like n8n_create_credential, n8n_delete_credential, and n8n_get_credential.

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 provides a critical prerequisite ('Requires n8n Enterprise/Pro license') indicating when the tool can be used, but lacks explicit guidance on alternatives (e.g., when to use create_credential instead) or exclusion conditions beyond the license check.

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