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

Beyond the readOnlyHint and destructiveHint annotations, the description adds important behavioral nuance: it reads from a cache rather than live API, so result freshness is qualified. It also discloses plan requirements and the key fields returned. This meaningfully informs an agent about behavioral consequences beyond the annotations alone.

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 compact and front-loaded: plan requirement, core action, filters, return fields, and caching caveat appear in two tight sentences. Every sentence adds useful information and none of it repeats the schema.

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?

The tool is simple with three optional boolean parameters and no output schema. The description covers plan requirements, data source, filters, and representative return fields. Some additional detail about the full return shape or pagination would improve completeness, but the description is largely sufficient for an agent to invoke this tool 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 description coverage is 100%, so each parameter is already documented by the schema. The description's mention of 'governance flags (monitor, notification rules)' reinforces that the parameters are filters, but it does not add detail beyond what the input schema already provides. Baseline 3 is appropriate.

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 uses a specific verb ('List'), identifies the resource ('Power Automate flows from the Power Clarity cache'), and notes the caching behavior, which distinguishes it from live-flow tools such as list_live_flows. It also states optional filtering by governance flags. This is specific and differentiates the tool from its siblings.

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 clearly states the Pro+ plan requirement and the key usage context: data comes from a stored snapshot, not the live Power Automate API. This strongly implies when the tool should be used over a live alternative, though it does not explicitly name an alternative such as list_live_flows or state when to prefer one.

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