n8n_delete_credential

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

No annotations are provided, so the description carries the full burden of disclosing behavioral traits. It only restates the delete action, offering no information about permanence, irreversibility, required permissions, or potential side effects. This adds no value beyond the tool name.

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, short sentence that is front-loaded with the verb and resource. It contains no redundant or filler content, making it appropriately concise for such a straightforward operation.

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?

This tool is a destructive operation with no annotations and no output schema, yet the description only states the action. It fails to mention whether deletion is permanent, if any confirmation is needed, or any other behavioral context. The description is insufficient for an agent to fully grasp the operation's implications.

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 documents the single parameter, credential_id, with a description ('ID de la credencial'), and coverage is 100%. The description does not add any extra semantic detail, so the baseline score of 3 applies.

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, 'Eliminar una credencial,' clearly states a specific verb (delete) and a specific resource (credential). It unambiguously distinguishes this tool from siblings like n8n_get_credential, n8n_create_credential, and n8n_update_credential.

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 provides no explicit guidance on when to use this tool versus alternatives, nor any exclusions or prerequisites. The usage is implied by the tool name and sibling context, but the description itself does not offer any contextual direction.

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