n8n_delete_workflow

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

Discloses default backup behavior, which is important for a destructive action. However, with no annotations, it doesn't mention permissions, undoability, or error handling, leaving gaps.

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?

Two clear, front-loaded sentences with no unnecessary words. Efficient and scannable.

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 delete action with backup note, but missing output description (no output schema) and safety context. Slightly above minimum due to backup disclosure.

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%, so baseline 3. Description adds no extra meaning beyond the schema's property descriptions (workflow_id, server_name).

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?

Clearly states verb 'Delete' and resource 'workflow from an n8n server'. The backup note adds specificity. Distinct from siblings like n8n_create_workflow or n8n_restore_workflow.

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?

Implies deletion usage but no explicit when-to-use, when-not-to-use, or comparisons with sibling tools like n8n_activate_workflow or n8n_export_workflow.

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