n8n_delete_workflow

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

The description adds value beyond the annotations by emphasizing 'Permanently delete' and 'cannot be undone', reinforcing the destructive nature. The annotations already set destructiveHint:true, but the description provides contextual clarity on irreversibility.

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 consists of two sentences, both front-loaded with essential information. No redundant or unnecessary words, achieving high conciseness while conveying all necessary details.

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 simple delete operation with one parameter and no output schema, the description is complete. It states the action, permanence, and irreversibility, which is sufficient for correct tool invocation.

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 parameter 'id' described as 'Workflow ID to delete'. The description does not add any additional semantic meaning beyond that, so it meets the baseline of 3 but does not exceed it.

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 'Permanently delete a workflow', specifying the verb (delete) and resource (workflow). This distinguishes it from sibling tools like n8n_create_workflow or n8n_update_full_workflow, which perform different operations.

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 includes 'This action cannot be undone', which serves as a warning and implicit guideline not to use this tool if reversibility is needed. However, it does not explicitly list alternatives or when not to use it, so it's clear but slightly lacking in exclusion details.

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