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

Annotations declare readOnlyHint=false and openWorldHint=true but say nothing about cost; the description adds that it spends workspace LLM budget bounded by the token's cost cap and runs synchronously. That is genuine context beyond the structured fields, though side effects, idempotency, and the needs_confirmation/approval path are not surfaced here.

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 sentences, front-loaded with the core action before the source-selection and input-format details; every sentence carries information. Slightly dense in the final clause but no wasted text.

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 7-parameter mutation with no output schema, it covers execution mode, source selection, cost implications, and input format. The main gap is that return values are only described as 'its outputs synchronously', leaving the response shape underspecified without an output schema to compensate.

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?

With 100% schema description coverage the baseline is 3, but the description adds concrete meaning by giving example input envelope shapes ({"kind":"chat","messages":[…]} / {"kind":"form","values":{…}}) and clarifying the draft-vs-published default for source/version. This goes beyond restating the schema.

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 and resource ('Execute a flow and return its outputs synchronously'), which clearly separates it from read-style siblings like workbench_flows_get or workbench_flows_list. It does not explicitly name an alternative tool, so it falls short of the 5-level sibling differentiation, but the action is unambiguous.

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 explains that draft runs by default and that source:"published" (with optional version) runs the live version, which is useful conditional guidance. However, it never states when to prefer this over adjacent tools such as workbench_flows_schedules_run_now or caliper_evals_run, leaving usage primarily implied.

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