Microsoft 365 Core MCP Server

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false, indicating this is a mutable, potentially destructive tool with non-idempotent operations. The description adds minimal behavioral context beyond this - it mentions 'zero-trust security' as context and lists example controls (MFA, device compliance, location-based), but doesn't elaborate on permissions needed, rate limits, or specific destructive implications. The description doesn't contradict annotations, but adds only modest value.

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, efficient sentence that packs substantial information: the action, resource, context ('zero-trust security'), and examples. There's no wasted language. However, it could be slightly more front-loaded by moving the examples to a second sentence for better scannability, preventing a perfect score.

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 tool's complexity (8 parameters, nested objects, destructive operations) and lack of output schema, the description is minimally adequate. It identifies the resource and context but doesn't explain return values, error conditions, or operational constraints. The annotations cover safety profiles, but for a complex security management tool, more guidance on usage patterns and outcomes would be beneficial.

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?

With 100% schema description coverage, the input schema already documents all 8 parameters thoroughly. The description adds no parameter-specific information beyond what's in the schema. It mentions 'MFA, device compliance, and location-based controls' which loosely map to some parameters, but doesn't provide syntax, format, or usage details. The baseline score of 3 is appropriate when the schema does all the heavy lifting.

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 tool's purpose: 'Manage Azure AD conditional access policies for zero-trust security including MFA, device compliance, and location-based controls.' It specifies the verb ('manage'), resource ('Azure AD conditional access policies'), and provides examples of security controls. However, it doesn't explicitly differentiate this from sibling tools like 'manage_defender_policies' or 'manage_exchange_policies', which prevents a perfect score.

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 alternatives. It doesn't mention prerequisites, appropriate contexts, or exclusions. While it hints at 'zero-trust security' as a context, this is too vague for practical guidance. There's no comparison to sibling tools like 'manage_security_alert_policies' or 'manage_compliance_frameworks' that might overlap in security management.

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