Delete workflow

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

Annotations already declare destructiveHint: true, so the description does not need to repeat that. However, it adds the context of 'Permanently' and 'exact confirmation', which are beyond the annotations. This provides additional behavioral disclosure about irreversibility and safety, earning a score above baseline.

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 sentence with no extraneous words. It is front-loaded with the action and includes the key constraint. Every word serves a purpose, making it highly concise and well-structured.

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 the tool has an output schema (exists), the description can omit return value details. It covers the core behavior (permanent deletion, confirmation required) but could be more complete by mentioning alternatives like n8n_workflows_archive for non-permanent deletion. Overall, it is adequate but not exhaustive.

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 50% (only confirmation has a description). The tool description adds 'exact confirmation' which aligns with the confirmation parameter but does not describe workflowId beyond the schema's pattern. For a 2-parameter tool with 50% coverage, the description adds some value but not enough to compensate fully.

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 'Permanently delete one workflow after an exact confirmation' clearly states the action (delete), resource (workflow), and a key constraint (confirmation). It distinguishes the tool from siblings like n8n_workflows_archive (archive vs permanent delete) and n8n_workflows_get (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 implies usage for permanent deletion after confirmation but does not provide explicit when-to-use or when-not-to-use guidance, nor does it mention alternatives like archiving. The confirmation requirement is a guideline, but lacking exclusions limits the score.

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