Delete credential

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

Beyond the annotations (destructiveHint=true), the description discloses that deletion 'can break every referencing workflow,' that no secret or rollback is returned, and that it requires 'unsafe mode plus credential-delete permission.' It also describes the return value. This adds significant behavioral context beyond what annotations alone provide.

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 three dense sentences, front-loaded with the core action and consequence. Every sentence provides necessary information—side effects, ID requirements, prerequisites, and return behavior—with no filler or repetition.

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?

Despite the tool's simplicity (one parameter), the description covers the essential context: side effects, parameter identification, prerequisites, permissions, and return value. An output schema exists, and the description still adds value by explaining the request-bound response. It is fully complete for an agent to safely invoke this destructive operation.

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%, so the baseline is 3. The description adds crucial semantics by specifying that credentialId 'must be the stable ID from n8n_credentials_list, get, or create; a credential name or type is not accepted.' This goes beyond the schema's 'Stable ID' description and clarifies valid sources and invalid alternatives.

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 'Permanently delete one stored credential' – a specific verb and resource with the permanent and singular scope. It distinguishes this from sibling tools like n8n_credentials_update and n8n_credentials_test by focusing on deletion and its irreversible nature.

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 advises to 'Scan all n8n_credentials_usage pages first, or update when replacement is enough,' giving clear guidance on prerequisites and when to prefer the update tool. It also notes the permission requirement, providing a complete usage context.

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