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

Annotations already declare readOnly/destructive=false, and the description adds genuinely useful non-obvious behavior: node inputs/outputs are truncated for transport and the full record lives in the flow's dev drawer. It also implies no auth caveats beyond what the schema documents, so this is solid but not exhaustive.

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?

Three dense sentences, front-loaded with what is returned before the usage guidance. Slightly editorial ('instead of guessing') but every sentence carries routing or return-shape information.

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, yet the description fully describes the return shape (per-node timeline, inputs, outputs, durations, error), the truncation caveat, and the flowId vs executionId selection. Nothing an agent needs to call or interpret it is missing.

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 coverage is 100%, so baseline is 3, but the description adds the key interaction rule: pass executionId to inspect one run, or just flowId for the most recent runs (echoing that limit is ignored when executionId is set). That interaction meaning goes beyond the per-parameter schema text.

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 resource and scope: 'recent executions with per-node timelines' plus what each node received, produced, took, and its error. This is clearly distinguishable from siblings like workbench_flows_get or workbench_tasks_run_view.

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 triggering condition ('when a run misbehaves instead of guessing') and routes the agent forward to workbench_flows_edit_text for the fix. It does not, however, name alternative read tools (e.g. caliper_traces_get or workbench_tasks_run_view) or state when not to use this.

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