Delete credential

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

Beyond annotations (destructiveHint=true), the description adds that deletion is permanent and requires exact confirmation. It explains the confirmation guard format, giving the agent crucial behavioral context without contradicting annotations.

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 that front-loads the action and resource, with no wasted words. Every part of the description is informative and necessary.

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?

Given the presence of output schema and annotations, the description adequately covers the destructive nature and confirmation requirement. However, it lacks information about permissions, side effects, or what happens to related data (e.g., workflows using the credential).

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 50% (only the 'confirmation' parameter has a detailed description in the schema). The tool description does not add any parameter-level meaning, especially for 'credentialId' which lacks schema description. The description 'after exact confirmation' hints at the confirmation parameter but does not explain its format in detail.

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 (delete) and resource (stored credential), and includes the confirmation guard. This distinguishes it from sibling tools like n8n_credentials_update or n8n_tags_delete.

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 implies use for deleting a credential but does not provide explicit guidance on when to use this tool versus alternatives, nor does it mention when not to use it. No prerequisites or exclusions are given.

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