Delete n8n Credential

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

Annotations already declare destructiveHint=true, but the description adds the concrete consequence that workflows will break, which is valuable beyond the annotation. The word 'Permanently' conveys irreversibility, supplementing the idempotentHint=false annotation with user-facing impact.

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 only two sentences plus a small Args block that mirrors the schema. It is front-loaded with the essential purpose and consequence, with no filler or redundant safety caveats.

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 single-parameter delete tool, the description adequately covers what the tool does, its permanence, and its main side effect (breaking workflows). Given the rich annotations (destructiveHint, idempotentHint) and lack of output schema, no additional return values or prerequisites are necessary for the agent to use it correctly.

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 input schema covers the sole parameter 'id' with a description already ('Credential ID to delete'), and the description repeats this same information. Since schema coverage is 100%, the description adds no new parameter semantics, giving the baseline score of 3.

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 tool's function: 'Permanently delete a credential.' This is a specific verb-resource pair and distinguishes it from sibling delete tools (e.g., delete_workflow) by explicitly naming the target resource. The additional warning about workflows breaking adds context without ambiguity.

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 usage for intentionally removing credentials and warns that 'Workflows using it will break,' which provides clear context for when to invoke it. However, it does not explicitly mention alternatives or exclusions (e.g., use update_credential to modify), so it lacks the explicit when-not guidance required for a 5.

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