PowerPlatform MCP

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

No annotations are provided, so the description carries full burden. It fails to disclose whether this is a read-only operation, pagination behavior (beyond the maxRecords parameter), or what constitutes 'business rules' in this specific platform context.

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 single sentence is front-loaded with the action and contains no filler. However, extreme brevity comes at the cost of guidance and context, preventing a score of 5.

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?

With output schema present and full parameter schema coverage, the description meets minimum needs for a list operation. However, it lacks usage context (when to prefer this over query-records or the singular version) and behavioral expectations.

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 clear descriptions for activeOnly, maxRecords, and environment. The description adds no parameter-specific guidance, but with such high schema coverage, the baseline applies.

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 verb (Get), resource (business rules), and scope (all, in the environment). It implicitly distinguishes from sibling 'get-business-rule' (singular) by specifying 'all', though it doesn't explicitly mention when to use each.

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 'get-business-rule' (singular) or 'query-records'. No mention of prerequisites, rate limits, or performance considerations when retrieving large rule sets.

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