PowerPlatform MCP

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

No annotations are provided, so the description must carry the full burden. It discloses output format options (XAML vs. structured summary) and identifies the target as a 'classic' workflow type, but fails to mention safety properties (read-only), error behaviors, or authentication 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?

The description is a single, information-dense sentence that front-loads the core action. Every term ('specific', 'classic', 'XAML', 'structured summary') serves to differentiate scope or output format without redundancy.

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 retrieval tool with a simple 3-parameter schema and no output schema, the description adequately covers the core function. However, given the lack of annotations, it leaves gaps regarding error handling, default environment resolution, and the distinction between classic workflows and modern flows.

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?

With 100% schema description coverage, the baseline is appropriately set at 3. The description reinforces the summary parameter's purpose by mentioning 'structured summary' and 'XAML definition', but does not add significant semantic detail beyond what the schema already provides for workflowId or environment.

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 ('Get') and resource ('classic workflow'), and implicitly distinguishes from siblings via 'specific' (contrasting with get-workflows) and 'classic' (contrasting with get-flow-definition). However, it does not explicitly reference sibling tools to clarify selection criteria.

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 provides no explicit guidance on when to use this tool versus alternatives like get-workflows or get-flow-definition. It omits prerequisites, error conditions, or environment selection logic beyond the schema description.

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