PowerPlatform MCP

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

No annotations provided, yet description lacks disclosure of read-only safety, return format, pagination behavior beyond the parameter name, or error conditions. Only describes the filtered entity types.

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, front-loaded with verb and scope. Colon-separated list efficiently enumerates included types without redundancy. No filler words.

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?

Adequate for a list-retrieval tool with well-documented schema. Defines the entity set clearly, though could improve by noting it returns a collection/list given the absence of an output schema.

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?

While schema has 100% coverage, the description adds value by mapping the abstract 'non-cloud-flow' concept to the specific category types listed, reinforcing what the numeric category codes (0-4) represent in business terms.

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?

States specific action ('Get') and resource ('non-cloud-flow workflows'), distinguishing from cloud flows. Lists exact workflow types covered (background, business rules, actions, BPFs, on-demand), clearly defining scope.

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?

Implicitly distinguishes use case via 'non-cloud-flow' qualifier, suggesting when not to use it (avoid for cloud flows). However, fails to clarify relationship to sibling 'get-workflows' or when to prefer one over the other.

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