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

The description adds meaningful behavior beyond the annotations: it discloses that an already-solution flow returns an error without attempting migration, and that omitting solutionId migrates to the default solution. This supplements the idempotentHint and destructiveHint annotations with concrete edge-case behavior, though it does not mention success return format or admin permission requirements.

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: purpose/mechanism, error behavior, and optional parameter guidance. Every sentence carries distinct value and the most important intent is front-loaded.

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 relatively simple three-parameter write operation with rich schema descriptions and safety annotations, the description is nearly complete. It covers the core operation, the non-solution prerequisite, the already-solution error case, and default solution behavior. The only notable omission is what a successful response looks like, but the absence of an output schema makes this a minor gap rather than a critical one.

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 schema already documents flowName, solutionId, and environmentName well. The description reinforces that solutionId is optional and defaults to the default solution, but it largely repeats information already present in the input schema rather than adding substantial new meaning.

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 specific verb and object: 'Migrate a non-solution Power Automate flow into a solution via the admin migrateFlows API.' This clearly identifies the operation and distinguishes it from the read/list/update-focused sibling tools, especially set_live_flow_state and update_live_flow.

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 provides clear context: use this for non-solution flows, and it explicitly states the failure behavior when the flow is already in a solution. It does not explicitly name an alternative check or when-not scenario, but the boundary is clear enough for an agent to decide when to invoke this tool.

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