Render an execution as a per-node timeline

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. Description adds that output is a markdown table sorted by start time and is deterministic, which aligns with idempotentHint. No contradictions.

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?

Two sentences, front-loaded with purpose and output details, second sentence adds sibling differentiation. Every sentence is essential and no 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 simple read-only tool with one parameter, the description fully covers purpose, differentiation, output format, and determinism. Annotations and schema cover safety and parameter constraints. No gaps.

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 100% for the only parameter 'execution', which already states it must include data.resultData.runData. The tool description adds no additional meaning about the parameter beyond the action.

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?

Description clearly states the verb 'Render' and the resource 'n8n execution as a per-node timeline', and explicitly distinguishes from sibling 'execution.explain' by contrasting 'why' vs 'when'.

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?

Directly contrasts with execution.explain by specifying that this tool surfaces 'when' while the other surfaces 'why', providing clear guidance on when to use each. Does not mention other alternatives like execution.replay, but the explicit comparison is sufficient.

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