n8n_delete_workflow

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

No annotations are available, and the description merely restates the tool's name ('Eliminar un workflow') without disclosing that deletion is permanent, cascades to executions, or requires special permissions. For a destructive operation, this complete lack of behavioral disclosure is a critical gap.

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 concise sentence, front-loaded with the action, with no redundant words. While extremely terse, it is appropriately sized for a one-parameter delete tool, though it sacrifices informational depth.

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?

With no annotations, no output schema, and a minimal description, the tool lacks important contextual details such as return values on success, possible errors, or whether the workflow must be deactivated before deletion. For a destructive operation, the description is insufficiently complete.

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 provides 100% description coverage for workflow_id, including its type and description. The tool description adds no additional parameter details; the baseline is 3 for high coverage, and no further value is contributed.

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 uses a specific verb ('Eliminar'/'delete') and resource ('workflow'), clearly distinguishing it from sibling operations like n8n_update_workflow, n8n_activate_workflow, and n8n_get_workflow. It unambiguously identifies the action 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?

No guidance is provided on when to delete versus deactivate a workflow, nor any prerequisites such as deactivating the workflow first. The sibling n8n_deactivate_workflow offers an alternative that is not mentioned, leaving the agent without decision-making context.

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