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

With no annotations, the description carries the burden and discloses important behavior: the result is read-only, tied to the run start state, and a configuration snapshot rather than an exact reconstruction. It does not cover permissions, error behavior, or output size.

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?

The key purpose and timing warning are front-loaded, and the parameter caveat is compact. The sentence is dense but nearly all content is relevant, with only slight awkwardness in phrasing such as 'for the flow.'

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?

The description gives a useful high-level account of the return value and snapshot semantics, which matters because no output schema exists. However, for a four-parameter tool with no schema descriptions or annotations, it leaves important parameter meaning and invocation details incomplete.

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 0%, so the description must explain all four parameters. It clarifies configId and its relationship to a run's versionId, but leaves workspaceId and name entirely unexplained.

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?

The description identifies a specific resource and format: the final internal-format flow JSON. It also distinguishes this retrieval from inspecting run progress, though it does not use an explicit verb or name every relevant sibling.

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?

It gives clear timing guidance: call it once work is done, not to inspect progress. It also points to get_flow_instance as the source for configId and versionId, but does not fully contrast itself with all sibling retrieval tools such as get_flow_summary.

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