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

Annotations already declare readOnlyHint/destructiveHint/openWorldHint, so the safety profile is covered. The description adds genuinely useful behavior the annotations don't: node inputs/outputs are truncated for transport and the full record lives in the flow's dev drawer. That's an important expectation-setting detail for a read tool.

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?

Front-loaded with what the tool returns, then the when-to-use trigger, then parameter selection, then the truncation caveat — each sentence earns its place with no filler.

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?

No output schema exists, and the description compensates well by describing the return shape (per-node timelines, inputs/outputs, errors) and its truncation limit. Combined with 100% schema coverage and read-only annotations, an agent has everything needed to call and interpret this correctly.

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% — the schema already documents limit's default/max and its being ignored when executionId is set, plus the workspace auth nuance. The description's 'Pass executionId to inspect one run, or just flowId for the most recent runs' adds only marginal selection guidance beyond what the schema states, so the baseline 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?

States a specific verb+resource (inspect a flow's executions) and enumerates exactly what comes back: per-node timelines, inputs, outputs, durations, and the failing error. This is clearly distinguishable from siblings like workbench_flows_get or workbench_flows_run, which manage or trigger flows rather than return execution traces.

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?

Gives an explicit trigger — 'USE THIS when a run misbehaves instead of guessing' — and routes the agent to the follow-on tool (workbench_flows_edit_text) for fixing. It also clarifies executionId vs flowId selection. It lacks an explicit 'when not to use' or a comparison against trace-reading siblings, so it stops short of a 5.

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