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

Annotations already establish the safe read-only, non-destructive, closed-world profile, so the bar is lower; the description still adds real value by disclosing the visibility scoping (only flows the caller can see) and the summary-level nature of results. Pagination or result-limit behavior is not mentioned, which is the remaining gap.

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?

Two tight sentences, zero filler. The scoping statement comes first and the routing hint second, which is the right front-loading order.

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?

With no output schema, the description usefully names the returned fields (id, name, visibility, updatedAt) and points to the get tool for the full body, which covers the main agent questions. Only result-set size/pagination behavior is left unaddressed.

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?

There is one parameter (`workspace`) whose schema description is fully detailed, covering token-type behavior and overrides. The description adds nothing about it, relying entirely on the schema. Baseline 3 is correct when schema coverage is 100%.

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 (Lists) and resource (every flow) with scope (active workspace the caller can see), and explicitly names the sibling `workbench_flows_get` as the detail counterpart. An agent can separate this discovery tool from the dozens of other workbench_flows_* siblings at a glance.

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?

Clearly implies use this for enumeration and `workbench_flows_get` when the full orchestration body is needed, which is explicit alternative routing. It stops short of stating when-not to use it (e.g., when the id is already known) or any paging guidance, so it is strong but not fully exhaustive.

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