Microsoft 365 Core MCP Server

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

Annotations provide readOnlyHint=false, idempotentHint=true, and destructiveHint=false, covering key behavioral traits. The description adds context about what gets managed (profile, mailbox, licenses, auth methods) but doesn't disclose rate limits, authentication requirements, or mutation specifics beyond what annotations already indicate.

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?

Single sentence efficiently conveys scope. Front-loaded with the main purpose. Could be slightly more structured but wastes no words. Every element earns its place by specifying what gets managed.

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?

For a mutation tool with 3 parameters, 100% schema coverage, and annotations covering safety/idempotency, the description is adequate but minimal. No output schema exists, so some guidance on return values would help. The description covers what but not how or when, leaving gaps in practical usage context.

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 parameter documentation. The description mentions 'profile information, mailbox settings, licenses, and authentication methods' which provides context for the 'settings' parameter, but doesn't add significant meaning beyond what the schema already specifies for the action and userId 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 clearly states the tool manages user account settings with specific examples (profile information, mailbox settings, licenses, authentication methods). It uses a specific verb ('manage') and resource ('user account settings'), but doesn't distinguish from siblings like 'manage_azure_ad_apps' or 'manage_security_groups' which manage different resources.

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. The description doesn't mention prerequisites, appropriate contexts, or when to choose other user management tools. With many sibling tools managing different Microsoft 365 resources, this lack of differentiation is a significant gap.

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