list_flow_groups

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

With no annotations, the description carries the full burden. It does disclose the read-only nature (List) and the scope ('all'), but provides no details on return format, sorting, pagination, or access limitations. This is acceptable for a simple zero-parameter list but lacks depth.

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?

A single, front-loaded sentence that says exactly what the tool does and why. No fluff or 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 read-only list tool, the description is mostly complete. It explains the purpose and the resource. The absence of an output schema means the return format isn't described, but for a simple list operation, this is not a significant gap.

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 accepts zero parameters, so per the rubric the baseline is 4. The description adds no parameter information, but the schema already fully covers this (100% coverage vacuously). No further semantic benefit expected.

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 action (list), the resource (flow groups), and adds a helpful clarification (folders) plus a purpose ('to understand the organizational structure'). This distinguishes it from sibling tools like get_flow_group (single) and list_flows_in_group (flows within a group).

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 intended use case ('to understand the organizational structure') is implied, but there is no explicit guidance on when to use this tool versus alternatives. It does not mention exclusions or direct users to get_flow_group or list_flows_in_group for more specific needs.

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