list_flows_in_group

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

The description reveals the key behavioral nuance of recursion (default false, but can include nested subgroups), which is not apparent from the tool name alone. However, since no annotations are provided, the description does not cover other behavioral aspects like pagination, return format, or permissions, so transparency is partial.

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, front-loaded with the verb 'List' and the resource 'flows', with no redundant information. It is perfectly concise and well-structured.

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 simple two-parameter list operation, the description communicates the core functionality and the recursive option. However, the absence of annotations and output schema leaves gaps about the response structure (e.g., whether the list contains flow IDs or full flow objects) and any pagination behavior, making it only partially complete.

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 input schema covers both parameters with descriptions and defaults, achieving 100% coverage. The description does not add new parameter semantics beyond echoing the recursive option, so the baseline 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 tool lists all flows within a specific group, with an optional recursive behavior for nested subgroups. This distinguishes it from sibling tools like list_flow_groups (which lists groups) and search_flows (which searches), making the purpose unambiguous.

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 is provided on when to use this tool versus alternatives such as search_flows, unified_search, or list_flow_groups. The description explains what it does but not the preferred use case or exclusions, leaving the agent to infer the appropriate context.

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