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

Annotations already declare readOnlyHint=true, destructiveHint=false, so the safety profile is covered. The description adds real value beyond that by disclosing the returned summary fields (id, name, visibility, updatedAt) and the visibility scoping ('the caller can see'), which an agent needs since no output schema exists.

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 with zero waste; the core listing behavior is front-loaded and the get-for-detail note follows naturally.

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 annotations covering safety, a single fully documented parameter, and no output schema, the description properly compensates by naming the return fields and pointing to the detail tool. Only the full shape of each summary is left implicit, which is a minor gap.

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% and the workspace param already documents slug semantics, default/override behavior, and API-key treatment. The description adds nothing about the parameter, so baseline 3 applies since the schema does the heavy lifting.

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 ('Lists every flow in the active workspace') with clear scoping ('the caller can see'), and explicitly distinguishes itself from workbench_flows_get by noting it returns only summaries.

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?

Clear context for use (enumerate flows, choose one to inspect) and routes to the alternative (`workbench_flows_get`) when the full orchestration body is needed. No explicit when-not guidance, but the routing hint is strong and actionable.

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