PowerPlatform MCP

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

No annotations provided, yet description discloses no behavioral traits. Fails to mention log retention periods, whether results are real-time or delayed, performance implications of large hoursBack values, or that exceptionOnly filters for errors.

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?

Extremely concise single sentence with no wasted words. Verb-fronted structure. However, brevity comes at the cost of completeness for an 8-parameter tool.

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 complexity: 8 parameters with time-range defaults (hoursBack), exception filtering, and multi-environment support. Output schema exists but description omits what trace logs contain (execution duration, exception details, plugin step sequence).

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 coverage is 100%, establishing baseline 3. Description mentions 'filtering options' generically but adds no semantic context beyond schema (e.g., explaining correlationId traces request chains across plugins or that environment defaults to the current one).

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 the resource ('plugin trace logs') and hints at capabilities ('filtering options'), but borders on tautology by restating the tool name. Does not differentiate from siblings like 'get-entity-plugin-pipeline' (configuration) vs this tool's execution logs purpose.

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 on when to use this tool versus alternatives like 'get-entity-plugin-pipeline' or 'get-flow-runs'. Does not mention that this is for debugging plugin execution history or when correlationId filtering is appropriate.

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