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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds real behavioral context beyond them: results carry lifetime stats, and the canvas definition is deliberately omitted, which stops the agent from calling this tool hoping to get definition data and points it toward get_flow_definition. Pagination behavior is left to the schema.

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?

Three short sentences, front-loaded with the verb and resource and with zero filler. The sentence fragments ('Automation flows with lifetime stats.') are slightly telegraphic, but each carries distinct information.

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 read-only list tool with no output schema and four optional, fully documented parameters, the description covers what is returned at a high level (lifetime stats) and what is not (canvas definition). It stops short of describing result ordering or pagination semantics, but the cursor parameter in the schema partially covers that.

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 descriptions for limit (page size 1-100, default 25), status, trigger_type, and starting_after cursor, so the schema carries the parameter burden. The description adds nothing about these filters, which is acceptable at full coverage but leaves it at the 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?

States a specific verb and resource ('List flows') and clarifies the domain as 'Automation flows with lifetime stats', so the agent knows it returns flow records with aggregated metrics. It does not distinguish itself from the many flow siblings such as get_flow, get_flow_definition, or list_flow_sessions, so an agent still has to reason about which flow-listing tool applies.

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?

There is no explicit when-to-use guidance: nothing says to call this to enumerate or filter flows rather than to fetch a single flow with get_flow or to inspect runs with list_flow_sessions. The only directional hint is the negative statement that the canvas definition is not exposed, which implicitly routes definition lookups elsewhere.

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