n8n_delete_workflow

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

No annotations provided, so description carries full burden. It successfully discloses the destructive/irreversible nature ('cannot be undone'), but omits error conditions, cascade effects on executions, or return value details.

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?

Efficient two-sentence structure with information front-loaded. The '[UNIFIED]' prefix appears to be metadata leakage rather than intentional description content, slightly detracting from an otherwise clean structure.

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?

Adequate for a simple 2-parameter deletion tool with no output schema. Covers the essential safety warning for a destructive operation, but incomplete due to missing parameter documentation and lack of behavioral context (errors, side effects).

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 has 0% description coverage with two required parameters ('site', 'workflow_id'). The description fails to compensate by explaining parameter semantics, formats, or examples—critical gap given the zero schema documentation.

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?

Clear specific verb ('delete') + resource ('workflow'). The term 'Permanently' distinguishes this from sibling n8n_deactivate_workflow, making the scope unambiguous despite the '[UNIFIED]' metadata prefix.

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 warning 'This action cannot be undone' implies this is for permanent removal (vs temporary deactivation), but lacks explicit guidance on when to use delete versus n8n_deactivate_workflow or prerequisites like workflow state checks.

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