n8n: Transfer credential

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

Annotations already declare readOnlyHint=false, destructiveHint=true, and idempotentHint=false, so the agent knows this is a destructive, non-repeatable mutation. The description adds genuinely useful enterprise-licensing context beyond the annotations, but it never clarifies the core behavioral question for a 'transfer' — whether the credential is moved (removed from the source) or shared/copied, and what happens to nodes or workflows still referencing it.

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 efficient sentence plus a prerequisite clause, which is well front-loaded. However, the '[UNIFIED]' tag conveys nothing actionable to an agent and consumes space that could have held parameter or behavioral detail.

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 and zero parameter documentation, the definition is thin: an agent knows what it does and that a license is needed, but not what each argument means or what side effects to expect. The licensing note is helpful, but the definition should carry more weight given the absence of structured documentation.

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%, so all three parameters (site, credential_id, destination_project_id) are undocumented in structured data. The description only indirectly hints at the destination parameter via 'another project' and says nothing about the meaning or format of site or credential_id, leaving the burden unmet.

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 states a specific verb and resource: 'Transfer a credential to another project.' The resource (credential) and target (project) are unambiguous, which separates it from the sibling transfer tool that acts on workflows, though the description never names that distinction explicitly.

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 only contextual statement is a licensing prerequisite ('Requires n8n Enterprise/Pro license'). There is no guidance on when to use transfer versus recreating the credential in the destination project, no mention of prerequisites such as owner role on both projects, and no note on what happens if the destination already has an equivalent credential.

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