list_flows

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

Annotations already declare readOnlyHint=true, so the description is consistent with a read-only operation. It adds nothing beyond the annotation about behavior (e.g., no mention of pagination, default limit, or result shape), which is acceptable given the low bar for simple list operations, but it doesn't enrich the behavioral context further.

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, focused sentence that front-loads the core purpose and lists filters efficiently. Every word earns its place, with no redundancy or filler.

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 list tool with no required parameters and full schema coverage, the description covers the essential functionality. It lacks an explicit note about return values (no output schema exists), but given the simplicity and the absence of complex behavior, it is adequately complete for an agent to invoke correctly.

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 coverage is 100%, with each parameter described (limit, query, active, category). The description's mention of 'filter by name, category, or active status' restates the schema without adding new meaning or usage nuances, so it stays at baseline.

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 Flow Designer flows and optionally filters by name, category, or active status. It uses a specific verb ("List") and resource ("Flow Designer flows"), distinguishing it from sibling tools like get_flow or create_flow. The mention of filters adds precision.

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 usage through the optional filters, but it does not explicitly state when to use this tool over alternatives like list_process_automations or get_flow. There is no exclusionary guidance, so it meets only the 'implied usage' level.

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