get_flows

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

No annotations are provided, so the description carries the burden. It discloses that the tool returns a FlowList grouped by tabs/nodes/subflows with summary stats, which is useful behavioral context. However, it does not mention any side effects, performance implications of fetching all flows, or authentication requirements.

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 concise and front-loaded, with exactly two sentences. The first line is a clear summary, and the second line specifies the return structure without redundancy.

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?

For a zero-parameter getter with an output schema, the description is reasonably complete. It covers the scope (all flows), the return structure, and the grouping. However, it lacks guidance on how this tool differs from get_flows_formatted and does not mention any pagination or truncation behavior.

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?

The tool has zero parameters, and the schema covers 100% of the parameter space. The description adds no parameter-specific semantics, but none are needed.

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 tool gets all flows with summary statistics and specifies the grouping (tabs/nodes/subflows), distinguishing it from sibling get_flow (single) and get_flows_formatted. The verb 'Get' and resource 'flows' are specific.

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?

The description implies the tool is used to retrieve all flows for summary/overview purposes, but it does not explicitly state when to use it over alternatives like get_flows_formatted or visualize_flows, nor any exclusions. The 'Returns' line provides context but no explicit usage guidance.

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