Microsoft 365 MCP Server

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

Annotations declare readOnly=true and destructive=false. Description adds scope context (User/Group/Site targets) but omits pagination behavior (fetchAllPages), OData query pattern explanations, or rate limit details expected for a read-heavy list operation.

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 is front-loaded and efficient. However, brevity is excessive for a tool with 11 optional query parameters; a second sentence noting all parameters are optional or describing pagination would improve structure without harming conciseness.

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?

Critical gap: description mentions targeting User/Group/Site but schema provides no explicit target parameters (e.g., user_id), leaving ambiguity. Also fails to contextualize the OData query pattern (filter, select, expand) for a Microsoft Graph API tool with complex querying capabilities.

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%, documenting all 11 OData-style parameters (filter, select, expand, etc.). Description adds no parameter-specific guidance, earning baseline 3. No contradictions.

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?

Clear verb 'Retrieve' and resource 'Drive resources' identifies the tool lists drive containers (not contents). Mentions scope 'User, Group, or Site' but doesn't distinguish from sibling 'get-drive-root-item' or clarify how targets are specified.

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?

Implies usage by stating the tool retrieves drives 'for a target User, Group, or Site', indicating scope. However, lacks explicit when-to-use vs. alternatives and omits how to specify the target entity given the schema lacks explicit user/group/site parameters.

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