n8n_transfer_credential

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. While 'transfer' implies moving the credential from one project to another, the description does not mention side effects such as removal from the source project, permission requirements, impact on workflows using the credential, or whether the operation is reversible.

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, front-loaded sentence with zero wasted words. It immediately communicates the action and target, making it easy for an agent to parse quickly.

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 simple two-parameter operation with fully documented schema fields, the description is minimally viable. However, the absence of any behavioral context, return-value expectations, or failure conditions leaves meaningful gaps for an agent deciding whether and how to invoke it safely.

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 100%, with both parameters already described as 'Credential ID' and 'Destination project ID'. The description adds no additional meaning or constraints beyond what the input schema provides, so the baseline score of 3 is appropriate.

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 ('Transfer'), a clear resource ('a credential'), and the target context ('to another project'). This precisely distinguishes it from sibling tools such as n8n_create_credential, n8n_delete_credential, and especially n8n_transfer_workflow, which shares the transfer verb but targets a different resource.

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?

No guidance is provided about when to use this tool instead of alternatives, such as creating a copy of the credential in the destination project or transferring a workflow. There are no prerequisites, exclusions, or context cues to help an agent decide between this and related project/credential operations.

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