n8n_delete_execution

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

The description merely restates the tool's function without adding behavioral context beyond the annotations. The destructiveHint annotation already signals that deletion is destructive; the description does not mention permanence, permissions, side effects, or any additional caveats.

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 with no filler. It conveys the essential purpose in five words and earns its place.

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 one-parameter mutation tool with destructiveHint annotation and no output schema, the description covers the core action and resource sufficiently. It lacks finer details like irreversibility or error behavior, but these are largely implied by the word 'delete' and the annotation, making it adequate but not rich.

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 schema fully documents the sole parameter 'id' with its type and description, so the description adds no parameter semantics. Schema coverage is 100%, so the baseline of 3 applies.

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 'Delete an execution record' names a specific verb (delete) and resource (execution record), clearly stating what the tool does. It distinguishes itself from sibling tools like n8n_get_execution, n8n_retry_execution, and n8n_list_executions, being the only execution deletion tool.

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 guidance is provided on when to use this tool versus alternatives such as n8n_retry_execution or n8n_delete_workflow. The description does not state any prerequisites, reversibility, or conditions for use.

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