Delete execution

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

The annotations already indicate destructiveness (destructiveHint=true). The description adds context by specifying 'Permanently delete' and 'after exact confirmation,' which explains the safety mechanism. It does not, however, mention potential side effects like cascading data deletion.

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, well-structured sentence with no extraneous information. It front-loads the core action and safety requirement.

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?

Given the tool's simplicity (2 parameters, destructive action with confirmation) and the availability of annotations and an output schema, the description adequately covers the essential context. It could mention the irreversible nature more explicitly, but overall it is sufficient.

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 50% (only 'confirmation' has a description). The description does not add meaning beyond the schema; it mentions 'exact confirmation' but does not clarify the 'executionId' parameter or the exact format of the confirmation string (though the schema does). The description fails to compensate for low coverage.

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 the action ('delete'), the resource ('saved execution'), and the condition ('after exact confirmation'). It distinguishes the tool from sibling tools like n8n_executions_get, n8n_executions_list, and n8n_executions_retry, making the purpose unambiguous.

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 description implies usage (use when you want to delete an execution) but provides no explicit guidance on when not to use it, such as alternatives for soft deletion or bulk operations. No comparison with sibling tools is given.

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