n8n_delete_credential

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

The destructiveHint annotation already flags the destructive nature, and the description adds the authorization requirement ('owner only'). It does not mention irreversibility or impact on workflows using the credential, but the annotation lowers the burden and the added auth context is valuable.

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 a single clear sentence with no wasted words. The core operation is front-loaded, and the permission qualifier is placed compactly in parentheses.

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 one-parameter delete operation with a destructiveHint annotation, the description covers the essential context: what is deleted and under what authorization. It could mention permanence or downstream effects, but these are not critical for invoking the tool 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?

Schema coverage is 100%, with the 'id' parameter already described as 'Credential ID to delete'. The tool description adds no extra semantic detail about the parameter beyond what the schema already provides, so the baseline score of 3 is appropriate.

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 states the exact operation and resource: 'Delete a credential'. The 'owner only' qualifier adds a scoping constraint that clarifies who can perform the deletion. This clearly distinguishes it from credential-related siblings like create, transfer, or schema retrieval.

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 clearly implies use when a credential needs to be removed and communicates the owner-only restriction. It does not explicitly discuss alternatives or when not to use it, but for a delete operation this context is largely sufficient.

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