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

Annotations already declare readOnlyHint=true and destructiveHint=false; the description adds meaningful behavioral context such as admin account requirements, owner-mode scoping to personal + team flows with full definitions, and time-bounded pagination semantics. It doesn't cover auth failures or rate limits, but the main behavioral traits are disclosed.

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 tightly written and well structured: it front-loads the core purpose and return fields, then layers mode, search, and pagination details in a logical order. Every sentence earns its place without repeating what the schema already documents.

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?

There is no output schema, but the description names the returned fields and sufficiently explains modes, search, and pagination for a listing tool. The reference to 'full definitions' is slightly ambiguous relative to the listed return fields, and edge/error cases aren't covered, but overall it is adequate for the tool's complexity.

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%, so the baseline is 3. The description adds value by clarifying that mode=owner is the default and includes personal + team flows with full definitions, that admin mode requires an admin account, and how timeoutSeconds and continuationUrl work together for pagination. This goes beyond the schema's existing descriptions.

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 Power Automate flows in an environment') and enumerates the returned fields, which clearly distinguishes it from generic list tools. It doesn't explicitly differentiate from sibling list_store_flows, so it stops short of a 5.

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?

Provides strong conditional guidance: mode=owner vs admin with the admin account requirement, search filtering by displayName, and time-bounded pagination with continuationUrl handoff. It gives clear context for how to use the tool, though it doesn't explicitly state when to prefer this tool over list_store_flows.

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