Start a flow run

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

Since no annotations provide any safety or behavioral hints, the description carries the full burden and does well: it states that flows execute for real, that confirm:true is required for live changes, that it uses the Power Automate service scoped to 'flow', and that it is unverified. This is exactly the kind of behavioral transparency expected for a mutation.

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 four sentences with no filler. It front-loads the core action in the first sentence, then immediately states the trigger constraint, the real-world consequence, and the verification incompleteness. Every sentence earns its place.

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 an 8-parameter mutation tool with no output schema and no annotations, the description gives the critical runtime context: trigger constraints, live side effects, and confirmation. It could also mention the dry-run mode when confirm is false or return/status semantics, but those are not essential and are partially implied by the parameter.

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 the baseline is 3. The description adds value by clarifying that the flowId must point to a manually triggered flow, that the payload is optional, and that confirm must be true for live execution, which supplements the schema more than just repeating its fields.

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 and resource: 'Start a run of a manually triggered cloud flow'. It also disambiguates by stating that scheduled and event-driven flows are not started this way, helping the agent distinguish this from flow-management 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?

It explicitly names the when and when-not: only manual or agent-callable triggers can be used, and scheduled/event-driven flows run on their own. It also flags the confirmation requirement for live changes, but does not name a specific sibling tool to use instead, so the differentiation is not fully explicit.

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