Render an execution as a per-node timeline

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

While annotations already declare readOnlyHint=true and idempotentHint=true, the description adds valuable behavioral context: output is a markdown table sorted by start time, and the tool is deterministic. This goes beyond what annotations inherently provide.

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 extremely concise: two sentences and one word, with no wasted content. It front-loads the core purpose, then provides comparison and output details. Every sentence earns its place.

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 low complexity (one parameter, rich annotations, and an output schema), the description is fully adequate. It explains the output format, ordering, determinism, and relationship to a sibling tool, leaving no significant 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 single parameter 'execution', which already documents the requirement for `data.resultData.runData`. The description does not add additional semantics beyond the schema, so a baseline score of 3 is appropriate.

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 'Render' and the resource 'n8n execution as a per-node timeline' with specific outputs (start offset, duration, items in/out, error flag). It explicitly distinguishes itself from the sibling 'execution_explain' by contrasting 'why' vs 'when', fulfilling the requirement to differentiate from siblings.

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 by stating it complements execution_explain and clarifies the differing purposes ('when' vs 'why'). However, it does not explicitly state when to avoid using this tool or mention additional alternatives beyond the named sibling.

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