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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful behavior beyond that: results are newest-first, and the version set differs depending on whether the flow is in a solution (all published versions) versus not (only versions that ran). It stops short of noting pagination/truncation behavior beyond the schema's default of 30.

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 the core action and ordering front-loaded, followed by the conditional scoping rule. Nothing is redundant, though the second sentence could be split into an explicit conditional for faster scanning.

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?

There is no output schema, so the description carries the burden of return-value context; it conveys ordering and which versions appear but not what a version record contains or how to page past `top`. For a read-only list tool with fully documented parameters, this is close to complete but leaves a modest gap on return shape.

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 description coverage is 100%, so flowName, environmentName, and top (max versions, default 30) are already documented in the schema. The description adds no format hints, naming conventions, or interaction between top and the newest-first ordering, so baseline 3 applies.

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 ("List a flow's versions") plus the ordering, which cleanly separates it from siblings like get_live_flow (definition) and get_live_flow_runs (runs). It never names a sibling explicitly, so an agent must infer the boundary rather than being routed.

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?

Usage is implied by the resource name rather than stated: there is no "use this when you need version history, use X for the current definition" guidance and no prerequisite note about needing a flow that exists in the environment. The solution-vs-other flow rule describes results, not when to choose this tool.

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