Delete a workflow on a live n8n instance

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

Since no annotations are provided, the description carries the full burden. It states that deletion is 'permanent', which is a key behavioral trait. However, it does not disclose other important behaviors such as whether the workflow must be deactivated first, whether associated executions are removed, or error conditions. The 'permanent' qualifier adds some value, but significant gaps remain.

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, front-loaded sentence that is easy to parse. It wastes no words, though it sacrifices informational content for brevity. It is appropriately concise for a simple operation, though it could be slightly more informative without losing efficiency.

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 output schema and no annotations, the description is the sole source of context. It covers the basic action but omits crucial details about side effects, error scenarios, or success/failure responses. Given the irreversible nature of deletion, more information is needed for safe and correct 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?

The input schema has only one parameter 'id' with no description, and schema description coverage is 0%. The tool description does not mention the parameter or its meaning. While the context implies 'id' is the workflow ID, this is not explicitly stated, leaving the agent to infer the semantics.

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 verb 'delete' and the resource 'workflow', and notes the action is permanent, distinguishing it from other delete operations on executions or credentials. It is specific and unambiguous.

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 provides no guidance on when to use this tool versus alternatives, no exclusions, and no mention of prerequisites (e.g., workflow must be inactive). Usage is only implied by the tool name and description, not explicitly stated.

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