n8n_delete_executions

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

No annotations are provided, so the description carries the full burden. It states 'delete' implying destruction, but lacks critical safety context: irreversibility warnings, behavior on partial failures (if some IDs don't exist), batch size limits, or required permissions.

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 brief (one sentence), but the '[UNIFIED]' prefix is structural cruft that wastes the front-loaded position. It is concise to the point of under-specification for a high-risk bulk deletion tool.

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 bulk operation, the description is dangerously incomplete. It lacks error handling details, confirmation requirements, or return value documentation (though no output schema exists). The minimal description does not match the risk profile of the operation.

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?

With 0% schema description coverage, the description completely fails to compensate. It does not explain what 'site' refers to (instance identifier?), nor the expected format of 'execution_ids' (UUIDs, integers, strings?). Both critical parameters remain undocumented.

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 'Bulk delete multiple execution records' with a specific verb and resource. The 'multiple' distinguishes it from the sibling tool 'n8n_delete_execution' (singular), though the '[UNIFIED]' prefix adds noise without value.

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 bulk tool versus the single 'n8n_delete_execution' alternative. While 'bulk' implies batch operations, there are no prerequisites, warnings, or selection criteria provided.

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