n8n_get_execution

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

Annotations indicate readOnlyHint=true, destructiveHint=false, and openWorldHint=true, covering safety and scope. The description adds valuable context beyond this: it specifies what data is returned (node outputs, error messages, timing, full logs) and the purpose (debugging, understanding data flow), which helps the agent understand the tool's behavior without contradicting annotations.

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 two sentences, front-loaded with the core purpose and followed by usage context. Every sentence adds value: the first specifies what data is retrieved, and the second explains when to use it, with zero wasted words or redundancy.

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 complexity (retrieving detailed execution data), annotations cover safety and scope, and the schema fully documents the single parameter. However, there is no output schema, and the description does not detail the return format (e.g., structure of logs), leaving a minor gap. It is mostly complete but could benefit from more on output specifics.

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 input schema has 100% description coverage, with the 'id' parameter documented as 'Execution ID from list_executions'. The description does not add further meaning about the parameter, such as format examples or constraints, so it meets the baseline of 3 where the schema does the heavy lifting.

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 verb 'Get' and the resource 'detailed execution data', specifying it includes node outputs, error messages, timing, and full execution logs. It distinguishes from siblings like n8n_list_executions (which lists executions) and n8n_delete_execution (which deletes), by focusing on retrieving detailed data for a specific execution.

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 provides clear context for usage: 'Essential for debugging failed workflows or understanding data flow.' It implies when to use this tool (for detailed analysis) but does not explicitly state when not to use it or name alternatives like n8n_list_executions for overviews, which keeps it from a perfect score.

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