n8n: Delete executions

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 agent knows this is a destructive, non-idempotent write. The description adds nothing beyond that: no statement of irreversibility, no behavior on invalid or partial ID lists, no permission requirements, and no mention that deletions cannot be undone. The "[UNIFIED]" prefix is unexplained noise.

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 short sentence with no filler, but it is under-specified rather than genuinely concise, and the opaque "[UNIFIED]" prefix consumes attention without conveying information.

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, two-parameter tool with 0% schema coverage and no output schema, the description carries the full burden and delivers almost none of it. An agent learns only that this is a bulk delete; it cannot tell what site selects or what a successful or partial failure looks like.

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 both parameters. "Multiple execution records" loosely hints that execution_ids is a list, but the description never explains what site means, what form the IDs take, or whether there is a batch size limit. It does not compensate for the schema gap.

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?

"Bulk delete multiple execution records" gives a specific verb (delete) and resource (execution records), and the words "bulk"/"multiple" separate it from the singular n8n_delete_execution sibling. It never names that sibling explicitly, so the differentiation is implied 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?

The word "bulk" implies this is the batch counterpart to a single-record delete, which is weak but real usage guidance. There is no statement of when to prefer it, no prerequisites, and no caution about confirming before mass deletion.

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