Microsoft 365 MCP Server

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

Annotations already provide readOnlyHint=false, destructiveHint=true, and openWorldHint=true, indicating this is a destructive mutation operation with open-ended parameters. The description adds minimal behavioral context beyond annotations - 'Update' confirms mutation, but doesn't elaborate on what gets destroyed (Excel data? navigation properties?), rate limits, or authentication requirements. The description doesn't contradict annotations, but adds little value beyond what annotations already convey.

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 extremely concise (one sentence), but this brevity comes at the cost of clarity. While technically concise, it's under-specified rather than efficiently informative. The single sentence doesn't front-load the most critical information and leaves too much ambiguity about what the tool actually does.

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 mutation tool with 6 parameters, no output schema, and complex nested objects, the description is inadequate. It doesn't explain what 'sort' means operationally, what gets returned (if anything), how to interpret the various IDs, or what the sorting behavior entails. The annotations help with safety profile, but the description fails to provide sufficient context for proper tool invocation given the complexity.

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 83% schema description coverage, the schema already documents most parameters well. The description adds no meaningful parameter semantics beyond what's in the schema - it doesn't explain what 'body' contains for sorting, how drive IDs relate to Excel files, or what the various path parameters represent. The baseline of 3 is appropriate given the high schema coverage, but the description doesn't compensate for the remaining 17% gap in parameter understanding.

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 'Update the navigation property sort in drives' is a tautology that essentially restates the tool name 'sort-excel-range' in different words. It doesn't specify what 'sort' means in this context (sorting Excel data? sorting navigation properties?), nor does it clearly distinguish this tool from sibling Excel tools like 'format-excel-range' or 'get-excel-range'. The purpose remains vague and ambiguous.

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. There are multiple Excel-related sibling tools (format-excel-range, get-excel-range, create-excel-chart, list-excel-worksheets), but the description doesn't explain when sorting is appropriate versus formatting or retrieving data. No context about prerequisites, alternatives, or exclusions is provided.

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