n8n_create_credential

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

With no annotations, the description must disclose behavioral traits itself; it only states 'Create a new credential', implying it adds rather than overwrites. It does not disclose whether a duplicate name is rejected, what data shape is required for a given type, project scoping behavior, or whether the credential is usable immediately.

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?

A single sentence containing exactly the essential action and object, front-loaded with the verb. No filler or repetition of schema details.

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 tool with a free-form nested object (data), no output schema, and no annotations, this one-sentence description leaves agents without guidance on how to construct valid data or what to expect in return. It doesn't mention consulting get_credential_schema or the required data structure for each credential type.

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 100%, so the schema already documents all four parameters. The description's 'specific node type' loosely points at the 'type' parameter but adds no meaning beyond the schema, which includes the httpBasicAuth example. Baseline 3 applies.

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 uses the specific verb 'Create' and identifies the resource as 'a new credential', which clearly distinguishes it from sibling operations like delete, transfer, or get schema. However, 'for a specific node type' is imprecise — the schema shows the type is a credential type like 'httpBasicAuth', not a node type. It doesn't name sibling tools to further disambiguate.

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 on when to use this tool, what prerequisites exist (e.g., obtaining the credential schema via n8n_get_credential_schema), or how it relates to credential deletion/transfer siblings. The only inference is that it is the creation counterpart, which is self-evident from the name and description.

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