powerplatform_list_flows

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description's 'List' aligns with that. The description adds useful context by saying the data is synthetic and scoped to a pinned development scope, but it does not disclose return shape, pagination, or behavior when no flows exist.

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 front-loaded sentence with no filler, no restatement of the tool name, and no wasted words. Every phrase contributes either the action, the resource, or the scope.

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 parameterless listing tool, this is nearly complete: it names the resource and scope, and the annotations cover safety behavior. The main gap is that 'pinned development scope' is unexplained jargon, and there is no output schema to clarify the returned metadata structure.

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 input schema has zero properties, so there are no parameters to document and schema coverage is effectively complete. Since there are no parameters, the description cannot add parameter-level meaning, but none is needed.

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 opens with a concrete verb ('List') and identifies the resource ('synthetic flow metadata') and scope ('pinned development scope'), so an agent can recognize this as a read-only flow listing tool. It does not say exactly what fields the metadata contains, but it is distinct from the unrelated sibling tools.

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 phrase 'from a pinned development scope' implies the tool should be used for development-scoped flow metadata, which is a useful usage constraint. However, it does not explicitly say when to prefer this tool over alternatives, why the data is synthetic, or what to use for production flow metadata.

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