Microsoft 365 MCP Server

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

While annotations declare readOnlyHint=true, the description adds no behavioral context beyond this. It does not explain what the 'range' operation returns (values, formulas, formatting), pagination behavior, or the implications of the optional flags (excludeResponse, etc.).

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 three words long, constituting under-specification rather than appropriate conciseness. It front-loads zero useful information and wastes the opportunity to orient the agent.

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?

Given the tool's complexity (7 parameters, hierarchical resource addressing) and the presence of rich structured data (complete schema, annotations), the description is inadequate. It fails to contextualize the required parameters or explain the Excel-specific addressing scheme.

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 all parameters already having mechanical descriptions. The description adds no semantic value about what driveId, driveItemId, or address represent, warranting the baseline score for high-coverage schemas.

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 'Invoke function range' is a tautology that restates the tool name without clarifying what it actually does. It fails to mention that it retrieves cell values/data from an Excel worksheet or distinguish it from siblings like format-excel-range or sort-excel-range.

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?

Provides no guidance on when to use this tool versus alternatives, nor does it explain the prerequisite hierarchy (drive → item → worksheet) required to construct a valid request.

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