Microsoft 365 Core MCP Server

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

Annotations already indicate this is a non-readOnly, non-idempotent, destructive tool. The description adds some context by mentioning 'shared resources like mailbox, calendar, and files' which helps understand what M365 groups entail, but doesn't provide additional behavioral details like permission requirements, rate limits, or specific destructive consequences beyond what annotations declare.

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 communicates the core purpose without unnecessary words. It's appropriately sized for a tool with comprehensive schema documentation, though it could be slightly more specific about the management scope given the multiple action types available.

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 tool with 7 parameters, destructiveHint annotation, and no output schema, the description is minimally adequate. It covers the basic purpose but lacks details about return values, error conditions, or the scope of different actions (get/create/update/delete). The comprehensive schema helps, but the description doesn't fully compensate for the missing output schema.

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 schema fully documents all 7 parameters. The description mentions 'shared resources' which loosely relates to the settings parameter but doesn't add meaningful semantic context beyond what the schema already provides. The baseline score of 3 reflects adequate parameter documentation through the schema alone.

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 as managing Microsoft 365 groups for team collaboration with shared resources. It specifies the resource (M365 groups) and the general function (manage), though it doesn't differentiate from sibling tools like 'manage_security_groups' or 'manage_distribution_lists' which handle different group types.

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 when to choose other sibling tools like 'manage_security_groups' for different group management needs. Usage is implied rather than explicitly defined.

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