n8n_delete_credential

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

With no annotations provided, the description carries the full burden of behavioral disclosure but fails entirely. It does not state that this is a destructive, irreversible operation, nor does it explain what happens to workflows that currently use this credential (failure vs. broken references).

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 brief at four words, but the '[UNIFIED]' prefix appears to be system metadata rather than useful description text, slightly degrading the signal-to-noise ratio. Otherwise, it is appropriately sized for front-loading.

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 zero schema coverage and no annotations, the description is insufficient for a destructive operation. It should explain the 'site' parameter's purpose, warn about permanent deletion, and clarify impacts on dependent workflows. As-is, it leaves critical safety and usage context undocumented.

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 0%—neither 'site' (which n8n instance) nor 'credential_id' (expected format, UUID vs. name) have descriptions. The tool description adds no parameter context to compensate for this gap, leaving the agent with no semantic understanding of the inputs.

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 core action (delete) and resource (credential), distinguishing it from sibling tools like n8n_create_credential or n8n_get_credential. However, the '[UNIFIED]' prefix appears to be metadata noise that doesn't aid understanding, and the description lacks scope specificity (e.g., whether this affects workflows using the 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?

No guidance provided on when to use this tool versus alternatives such as n8n_transfer_credential (which might preserve credentials by moving them) or n8n_update_credential. No mention of prerequisites (e.g., admin permissions) or irreversibility warnings.

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