Microsoft 365 MCP Server

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

Annotations already indicate this is a destructive, non-read-only operation (destructiveHint: true). The description adds no behavioral context beyond what annotations provide—no explanation of what 'format' means, what changes occur, side effects, or mutation scope. With annotations carrying the safety profile burden, the description contributes minimal additional transparency.

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?

While brief (single sentence), the description suffers from under-specification rather than effective conciseness. The jargon-heavy phrasing ('navigation property', 'drives') obscures meaning without delivering value. Key information (Excel formatting, visual styling capabilities) is buried under technical abstraction.

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 complex tool with 6 parameters, nested object structures (borders array, fill/font objects), and no output schema, the description is inadequate. It fails to explain the tool's domain (Excel formatting), the nature of the formatting operations (visual styling), or the relationship between the path parameters and the body content.

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% (>80%), establishing a baseline of 3. The description mentions no parameters, but the schema effectively documents the complex nested body properties (borders, font, fill) and path parameters without requiring additional textual support.

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 jargon ('navigation property') from underlying API metadata that fails to clarify the actual user-facing purpose. It mentions 'drives' (the container) rather than Excel ranges/cells (the actual target resource), and doesn't clearly indicate this is for formatting Excel cells despite the tool name and sibling get-excel-range suggesting this context.

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?

Description provides no guidance on when to use this tool versus alternatives (e.g., get-excel-range for reading, sort-excel-range for sorting), nor does it mention prerequisites like obtaining driveId or workbookWorksheetId from prior calls. The single sentence only states what the tool does, not when to invoke it.

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