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

Adds substantial behavior beyond the annotations: it discloses that execution 'Spends workspace LLM budget, bounded by the token's cost cap' and that results come back 'synchronously'. The cost/budget disclosure is exactly the kind of non-obvious operational consequence annotations (readOnlyHint=false, destructiveHint=false) don't capture, and it is consistent with them.

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?

Four tight sentences, front-loaded with the core action and result, then source semantics, cost, and input examples. Every sentence carries information; the only slight sprawl is the inline input examples, but they are useful.

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, but the description covers what matters: synchronous return of outputs, budget/cap implications, draft vs published selection, and input envelope shape. The confirmation/approval re-call flow (approvalId) is only documented in the schema, leaving a minor gap for a 7-param tool.

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 already 100%, so the baseline is 3. The description adds real meaning on top: it explains the `source` semantics (default draft vs published-with-optional-version) and illustrates the `input` envelope with concrete examples ({"kind":"chat",...}, {"kind":"form",...}) that the schema does not provide.

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 ('Execute a flow') and adds the key behavioral result ('return its outputs synchronously'). Combined with the draft-vs-published distinction, an agent can distinguish this from sibling tools like workbench_flows_get or workbench_flows_publish without opening a schema.

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?

Conveys the default behavior ('Runs the draft by default; pass source:"published" ... to run the live published version') and the cost context, which implicitly guides selection. However, it never states when to prefer this tool over alternatives (e.g. schedules_run_now, tasks_run_view) or any exclusions, so guidance is implied rather than explicit.

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