n8n_retry_execution

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

With no annotations provided, the description carries the full burden and successfully discloses that it creates a new execution rather than resuming the old one. However, it omits safety details like permissions required, idempotency, or error conditions (e.g., attempting to retry a successful execution).

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 appropriately concise with two information-dense sentences that front-load the action. Minor deduction for the '[UNIFIED]' metadata prefix which adds noise without value, but the core content has zero waste.

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 tool with two parameters and no output schema, the description adequately explains the core concept but leaves significant gaps. It fails to document the 'site' parameter, explain what constitutes a 'failed' state, or describe the return value behavior, which is critical given the lack of structured annotations or output schema.

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 has 0% description coverage, requiring the description to compensate, but it fails to explain either parameter. While 'execution_id' is loosely implied by 'failed execution,' the 'site' parameter (likely identifying the n8n instance) remains completely undocumented with no hints about format or valid values.

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 specific action ('Retry') and resource ('failed execution'), and distinguishes itself from siblings like n8n_execute_workflow by explaining it 'Creates a new execution with the same input data' rather than running fresh.

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 context by specifying 'failed execution,' indicating when to use the tool. However, it lacks explicit guidance on when not to use it or named alternatives like n8n_execute_workflow for new runs versus retries.

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