Microsoft 365 MCP Server

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

Annotations provide readOnlyHint=true, destructiveHint=false, and openWorldHint=true, covering the safety profile. The description adds no behavioral context beyond what annotations already declare - no information about what gets returned, rate limits, authentication needs, or Excel-specific behaviors. However, it doesn't contradict annotations, so it meets the lower bar when annotations are present but adds minimal value.

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 technically concise with only three words, this is under-specification rather than effective conciseness. The description fails to front-load essential information about what the tool does. Every word should earn its place, but 'Invoke function range' provides almost no value beyond the tool name itself, making it inefficient despite its brevity.

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 tool with 7 parameters (4 required), no output schema, and operating on Excel data, the description is severely inadequate. While annotations cover safety, the description fails to explain what Excel range data gets returned, format considerations, or how this fits within the broader Excel tool ecosystem. The agent would struggle to use this effectively without extensive trial and error.

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 100% schema description coverage, all 7 parameters are documented in the schema itself. The description adds zero parameter information - it doesn't explain the hierarchical relationship between driveId, driveItemId, workbookWorksheetId, and address, or provide Excel-specific context about address format. The baseline of 3 is appropriate when the schema does all the heavy lifting.

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 'get-excel-range' without adding meaningful context. It doesn't specify what resource is being retrieved (Excel range data), what the verb actually does (retrieve/read), or how it differs from sibling Excel tools like 'format-excel-range' or 'sort-excel-range'. The purpose remains vague despite the clear naming convention.

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 absolutely no guidance on when to use this tool versus alternatives. There's no mention of prerequisites (like needing an Excel file), comparison to sibling tools (like 'list-excel-worksheets' or other Excel manipulation tools), or appropriate contexts for invocation. The agent receives zero usage direction beyond what can be inferred from the tool name.

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