get_flow_version

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

Without annotations, the description must disclose behavioral traits. It implies a read-only operation ('Get') but does not mention permissions, side effects, or what happens if the version does not exist. The description provides minimal behavioral context.

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 description is a single sentence, 12 words, front-loaded with the core purpose. Every word is necessary, and there is no superfluous information. It is as concise as possible.

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 tool is simple (get by two IDs) and no output schema exists. The description fails to indicate what is returned (e.g., the version object details). It also does not clarify the relationship between flow and version. Context is incomplete for even a basic retrieval operation.

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 both parameters are fully described in the input structure. The description adds no extra meaning beyond the schema (e.g., clarifying formats or constraints). Baseline score of 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?

The description clearly states the verb 'get', the resource 'specific saved version of a flow', and the key parameter 'version ID'. It distinguishes from siblings like 'list_flow_versions' by specifying a single version retrieval. However, it could be more explicit about what constitutes a 'version' in this context.

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?

No guidance on when to use this tool versus alternatives such as 'get_version' or 'list_flow_versions'. No mention of prerequisites, exclusions, or context. The description is purely functional without any usage hints.

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