Microsoft 365 Core MCP Server

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

The description adds valuable behavioral context beyond what annotations provide. Annotations indicate destructiveHint=true (mutation operations) and readOnlyHint=false, but the description clarifies this includes both monitoring ('Monitor') and management actions ('manage'), specifically mentioning 'risk remediation actions' which implies destructive operations. This aligns with annotations while providing domain-specific context about what types of destructive actions are involved.

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: domain, scope, and key functional areas. Every word earns its place with zero redundancy or fluff. It's appropriately sized for a multi-function tool and front-loads the most important information.

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 (6 parameters, multiple action types, destructive operations) and the absence of an output schema, the description provides adequate but minimal context. It covers the tool's scope and destructive nature but doesn't explain return values, error conditions, or specific behavioral nuances of different actions. With annotations covering safety profile and schema covering parameters, the description meets minimum viable standards.

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 6 parameters thoroughly. The description mentions 'risk detections, risky users, and risk remediation actions' which loosely maps to the 'action' parameter enum values, but adds no specific syntax, format, or additional semantic meaning beyond what's already in the schema. This meets the baseline for high schema coverage.

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: 'Monitor and manage Azure AD Identity Protection including risk detections, risky users, and risk remediation actions.' It specifies the domain (Azure AD Identity Protection) and the main functional areas (risk detections, risky users, risk remediation). However, it doesn't explicitly differentiate this tool from potential sibling tools like 'manage_alerts' or 'manage_security_alert_policies' that might overlap in security monitoring.

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, specific scenarios where this tool is appropriate, or how it differs from other security management tools in the sibling list. The agent must infer usage solely from the description and parameter schema without explicit direction.

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