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

With readOnlyHint=true already declaring a safe read, the description adds context the annotation does not: it costs nothing, and it enumerates the exact payload fields (id, name, trigger type, steps, published state, last run), which substitutes for the absent output schema. No pagination or result-count behavior is disclosed, keeping it below 5.

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?

One sentence, front-loaded with the cost signal and the resource, with zero filler. The parenthetical trigger list and field enumeration are dense but each item earns its place by describing return contents.

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-param read tool with no output schema, the description effectively documents the return shape and the free-cost behavior, which is what an agent needs to call it. It stops short of noting pagination or how many flows come back.

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 takes zero parameters, so the baseline is 4; the description correctly indicates no filtering input is required. It cannot add parameter meaning because none exist, and 'the person's Flows' usefully implies scoping is implicit rather than passed in.

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?

States a specific verb (list) and resource (the person's Flows), and defines what a Flow is ('automations built in the eroq studio'), which separates it from create_flow, edit_flow, run_flow and get_flow_run. An agent can identify this as the enumeration tool without opening the schema.

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 'Free.' prefix signals this call has no cost, which implicitly favors it over paid siblings, but there is no explicit when-to-use guidance or named alternative (e.g. get_flow_run for a single run). Usage is implied rather than stated.

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