n8n_get_execution_data

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 successfully discloses the data scope ('full execution data including all node inputs and outputs'), implying a read-only operation that returns comprehensive execution details. However, it fails to mention safety guarantees, performance implications of fetching large execution logs, or response format details.

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 efficiently structured in two sentences with key information front-loaded. The '[UNIFIED]' prefix is unnecessary metadata noise that does not aid agent comprehension, slightly detracting from an otherwise concise presentation.

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 absence of annotations, output schema, and parameter descriptions, the description provides minimal but adequate context by clarifying the tool returns detailed node-level data. However, it should ideally elaborate on the return structure or data volume expectations for a data retrieval tool of this nature.

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 0% description coverage for both 'site' and 'execution_id' parameters. The description provides no parameter guidance, leaving ambiguity about what constitutes a valid 'site' identifier (URL, name, or ID) or execution_id format. While the parameter names are somewhat intuitive, the description fails to compensate for the complete lack of schema documentation.

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 execution data including all node inputs and outputs,' specifying the resource and scope. However, it does not explicitly distinguish this tool from the sibling 'n8n_get_execution,' which likely returns summary metadata rather than detailed node data.

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 implied usage context by stating it is 'Useful for debugging,' indicating when this detailed data is needed. However, it lacks explicit guidance on when to use this versus the sibling 'n8n_get_execution' or other alternatives, and omits any prerequisites or constraints.

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