Microsoft 365 MCP Server

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

The verb 'Update' aligns with readOnlyHint:false and destructiveHint:true (implying file modification), but the description fails to disclose what actually happens (e.g., whether it permanently reorders rows, requires specific permissions, or affects the workbook structure). It doesn't explain the openWorldHint implication either.

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 technically concise, but wastes space on implementation-specific terminology ('navigation property') rather than front-loading the user-facing action. Every word should clarify intent for the AI agent; instead it obscures the purpose behind API jargon.

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 destructive operation (destructiveHint:true) with nested objects and no output schema, the description inadequately explains success indicators, side effects, or the scope of modification. It doesn't clarify whether this sorts an existing named range or creates a sort configuration.

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 83%, providing decent documentation for driveId, includeHeaders, etc. However, the description adds no semantic context for parameters, particularly the required 'body' object which only contains an 'id' field marked 'Read-only' in the schema—a confusing constraint left unexplained.

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 uses technical OData jargon ('navigation property') rather than user-facing language. While it mentions 'sort' and 'drives', it fails to clearly state this sorts data within an Excel workbook/worksheet, despite the tool name 'sort-excel-range' and siblings like 'format-excel-range' suggesting Excel operations.

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 provided on when to use this versus format-excel-range or get-excel-range. No mention of prerequisites (e.g., requiring valid driveId/driveItemId) or that it modifies the actual spreadsheet file rather than just returning sorted data.

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