PowerPlatform MCP

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It successfully describes what the tool returns (triggers, actions, connectors), but omits operational details such as error handling when a flow doesn't exist, authentication requirements, or whether the data is cached versus live.

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, efficiently structured sentence that front-loads the core purpose. Every clause earns its place by distinguishing between the full definition and summary output modes without redundant verbiage.

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?

Given the tool has 100% schema coverage and an output schema exists, the description appropriately avoids redundant return value documentation. It adequately covers the tool's functionality by specifying the types of data returned (triggers, actions, connectors), which is sufficient for a read-only retrieval tool of moderate 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 description coverage is 100%, with all three parameters (flowId, summary, environment) adequately documented in the schema. The description references 'parsed summary' which aligns with the summary parameter, but adds no additional semantic context (like valid environment name formats) beyond what the schema already provides, warranting the baseline score.

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 clearly identifies the action ('Get') and resource ('Power Automate flow') and specifies the output content ('complete definition' or 'parsed summary of triggers, actions, and connectors'). However, it does not explicitly distinguish when to use this versus sibling tools like 'get-workflow-definition' or 'get-flows'.

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 implies when to use the 'summary' parameter versus full definition, but provides no explicit guidance on when to select this tool over alternatives like 'get-flows' (for listing) or 'get-workflow-definition' (for classic workflows), nor does it mention prerequisites like needing the flow ID.

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