n8n: Delete execution

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false, so the safety profile is covered. The description adds that the record is removed from execution history, but says nothing about permanence, whether execution data (logs/outputs) is also purged, or how a missing execution_id behaves.

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 the action front-loaded and no preamble. The second sentence mostly restates the first (delete = remove from history), so it earns only partial credit rather than being fully waste-free.

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?

This is an irreversible mutation with no output schema and both parameters undocumented, so the description carries the whole burden and does not meet it. Missing are the meaning of "site", whether deletion is permanent, and what an agent should expect on failure.

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 description coverage is 0% for two required parameters, and the description contributes no explanation of either. In particular the "site" parameter is left entirely undefined — an agent cannot tell whether it is an instance URL, a slug, or an environment name, which is a real risk for a destructive call.

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?

"Delete a single execution record" names a specific verb and resource, and "single" implicitly separates it from the bulk n8n_delete_executions sibling. It stops short of naming the alternative tool or a workflow-scoped variant, so differentiation is inferred rather than stated.

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?

Usage is only implied: the word "single" suggests this is for one-off deletions versus bulk cleanup, but there is no explicit when-to-use, when-not-to-use, or named alternative. An agent must infer the routing decision from the sibling list.

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