Get n8n Execution

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the agent knows this is a safe, non-destructive read. The description adds minor behavioral context (e.g., 'including output data' and response format options) but does not disclose additional traits like error behavior or data volume. With annotations covering safety, this is adequate.

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 compact, with a clear first sentence stating the purpose. The Args list is somewhat redundant with the schema but not excessively verbose. It is well-structured and front-loaded, though it could be tightened by omitting the parameter list.

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 simple get-by-ID tool with safe annotations and no output schema, the description covers the essential information: it retrieves details including output data, and supports markdown/json formatting. It does not detail return fields, but given the tool's simplicity and the presence of response_format, the description is sufficiently complete.

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 67%, and the description's Args list largely duplicates the schema's property descriptions. For response_format, the description mentions the enum values, which the schema already provides. No additional semantic meaning is added beyond the schema, so the baseline of 3 applies.

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 tool retrieves full details of a specific execution by ID, which is a specific verb+resource+scope. It distinguishes itself from sibling tools like n8n_list_executions (list vs. get), n8n_delete_execution, and n8n_retry_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 implies usage context: use when you need full details of a specific execution by ID. It does not explicitly mention alternatives or when-not-to-use, but the purpose is clear enough for an agent to infer when to invoke it. No misleading guidance is present.

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