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

Annotations already establish that this is a safe read-only operation, and the description adds meaningful behavioral context: error diagnosis comes from real n8n error data and is never guessed, and per-node output includes status, item count, duration, error, and a sample. It does not cover permissions, handling of missing executions, or size limits, but it is substantially informative beyond the 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 a single front-loaded sentence that immediately states the purpose and then lists the returned information. Every clause adds useful detail with no repetition or wasted prose.

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?

There is no output schema, and the description compensates well by explaining the return contents, including overall status, error diagnosis, and per-node fields. The main remaining gap is the lack of execution_id semantics, but for a one-parameter inspection tool the description is largely 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?

The schema has zero description coverage for the single required execution_id parameter, and the description does not mention the parameter at all. The phrase 'one execution' weakly implies an execution identifier is needed, but there is no guidance on where to obtain it or its expected format.

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 states a specific resource and scope: one execution, with overall status, error diagnosis, and per-node details. It clearly differs from listing or triggering executions, though it does not explicitly name the sibling alternatives such as list_executions or trigger_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 this is for inspecting a single execution but gives no explicit when-to-use guidance, prerequisites, or exclusions. It does not say to use list_executions first or clarify when not to use this tool.

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