PowerPlatform MCP

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. While it mentions the return includes 'complete XAML definition,' it fails to indicate whether this is a read-only operation, if there are rate limits, error conditions, or caching 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 consists of a single, efficient sentence of nine words that front-loads the action verb. Every word serves a purpose, identifying the operation, target resource, and return 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?

Given the complete input schema and existence of an output schema, the description adequately covers the core function by mentioning the XAML return format. However, with no annotations provided, the description lacks contextual details about error handling, authentication requirements, or behavioral constraints that would make it fully self-contained.

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?

The input schema has 100% description coverage for both parameters (workflowId and environment), establishing a baseline score. The description adds no additional semantic information about parameter formats, valid environment values, or the relationship between the parameters.

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 the specific verb 'Get' and identifies the resource as a 'business rule.' It distinguishes scope by specifying 'specific' (singular) versus the plural sibling 'get-business-rules,' and clarifies the return format includes the 'complete XAML definition,' which differentiates it from general workflow retrieval tools.

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 guidance on when to use this tool versus siblings like 'get-business-rules' or 'get-workflow-definition.' It does not indicate prerequisites such as requiring the workflowId format or permissions needed to access business rules.

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