n8n_delete_execution

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

With no annotations provided, the description carries full burden. It discloses the destructive nature ('removes the execution from history') but lacks details on permissions, idempotency, or whether this affects running executions given 'n8n_stop_execution' exists as a sibling.

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 short sentences with minimal waste. The '[UNIFIED]' prefix adds slight noise but the core message is efficiently delivered. Slight redundancy between 'Delete' and 'removes'.

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?

For a destructive operation with 0% schema coverage and no output schema, the description is inadequate. Missing: parameter semantics (especially 'site'), distinction from bulk delete operations, and confirmation of whether deletion is permanent or recoverable.

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 for both 'site' and 'execution_id' parameters. The description fails to compensate by explaining what 'site' refers to or confirming that 'execution_id' identifies the specific execution to delete.

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 'Delete a single execution record' with specific verb and resource. It effectively distinguishes from sibling tool 'n8n_delete_executions' (plural/bulk) by emphasizing 'single'.

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 explicit guidance on when to use this versus the bulk 'n8n_delete_executions' alternative. No prerequisites mentioned (e.g., whether execution must be stopped first).

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