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. It successfully clarifies the tool searches across both classic and Power Automate flow types (unified search behavior), but fails to disclose other behavioral traits like read-only safety, default result limits when filters are omitted, or pagination behavior.

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, front-loaded sentence with zero redundancy. Every word earns its place by defining scope and searchable dimensions. However, given the tool's complexity (8 parameters, many siblings), it borders on under-specification rather than optimal conciseness.

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 output schema exists and input schema is fully documented, the description meets minimum viability. However, with 8 optional parameters and numerous sibling retrieval tools, the description lacks guidance on default behavior when no filters are provided and omits differentiation from similar discovery tools, leaving contextual gaps.

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%, establishing a baseline of 3. The description adds minor semantic value by mapping user-friendly terms ('entity', 'state') to technical parameter names ('primaryEntity', 'statecode'), but does not elaborate on syntax requirements (e.g., logical name format for entities) or explain the purpose of parameters like 'includeDescription' or 'environment' beyond the schema definitions.

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 states the action ('Search') and resource ('workflows'), explicitly distinguishing that it covers both 'classic workflows and Power Automate flows'—a key scope distinction from siblings like get-flows or get-workflows. However, it stops short of explicitly contrasting when to use this versus those retrieval alternatives.

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 lists searchable fields (name, entity, description, category, state) which implies filtering usage, but provides no explicit when-to-use guidance or comparison to siblings like get-workflows or get-flow-inventory. The agent must infer this is for discovery/filtering versus direct retrieval.

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