Create a credential on a live n8n instance

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

No annotations are provided, so the description must disclose behavioral traits. It only says 'Create a new credential' and advises checking the schema, but does not mention side effects, permissions, return values, or error behavior. This leaves significant transparency gaps for a mutation operation.

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 two concise sentences, with the action stated first and the prerequisite second. Every word adds value, and the structure is front-loaded and easy to parse.

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?

The tool is relatively simple with 3 required params and no output schema. The description includes the critical prerequisite (checking the schema), but omits return behavior and any execution details. It is adequate for basic use but leaves gaps for a new user.

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?

The schema already describes type and data with examples, and the description adds important context that data fields depend on the credential type and must be obtained from the schema tool. This compensates for the 67% schema coverage and clarifies the nested structure.

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 action 'Create a new credential' with a specific resource, distinguishing it from sibling tools like get, delete, or list. The title adds context about a live n8n instance, reinforcing the purpose.

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 description explicitly instructs to check n8n_get_credential_schema first for required data fields, providing clear when-to-use guidance by naming a prerequisite sibling tool. It does not mention exclusions, but the requirement is actionable and specific.

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