PowerPlatform MCP

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

With no annotations provided, the description carries the full disclosure burden but reveals almost nothing about behavior: it doesn't explain pagination (despite maxRecords parameter), what constitutes a 'classic' workflow technically, whether inactive workflows are included by default, or what the output schema contains.

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?

Single sentence of 7 words with no filler. However, given the complexity of the Dynamics workflow ecosystem and dense sibling namespace, extreme brevity becomes under-specification rather than efficiency.

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?

Inadequate for the crowded tool namespace. With 20+ sibling tools including similar 'get-workflow-definition', 'get-flows', and 'search-workflows', the description fails to clarify scope boundaries, return value structure (despite output schema existing), or prerequisites for the 'environment' 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?

Input schema has 100% description coverage, so the schema documents parameters adequately. The description adds no parameter context, but baseline 3 applies since no compensation is needed for schema gaps.

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 resource as 'classic Dynamics workflows' using ecosystem-specific terminology that distinguishes it from siblings like 'get-flows' (modern Power Automate) and 'get-ootb-workflows'. However, it lacks explicit differentiation from 'search-workflows' and 'get-workflow-definition'.

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?

No guidance provided on when to use this tool versus alternatives like 'search-workflows' (which likely offers filtering) or 'get-workflow-definition' (which retrieves specific details). The agent cannot determine if this returns metadata or full definitions.

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