Microsoft 365 MCP Server

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

The 'Read-only' statement duplicates the readOnlyHint annotation without adding behavioral context (e.g., pagination behavior via fetchAllPages, OData query options like $filter/$search, or what properties are returned). With annotations covering safety profiles, the description fails to exploit the lowered bar to explain query capabilities or return structure.

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 brief (two sentences), but 'Represents a collection' is weakly front-loaded and wastes space on static resource description rather than actionable guidance. The second sentence merely echoes the readOnlyHint annotation.

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 13 parameters supporting complex OData-style queries (filter, search, expand, orderby, select) and no output schema, the description is insufficient. It fails to explain the query capabilities, pagination behavior, or the nature of returned worksheet metadata.

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, the schema fully documents all 13 parameters including pagination (top/skip), filtering, and projection options. The description adds no parameter-specific guidance, but the high schema coverage establishes a baseline score of 3 per the rubric.

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 identifies the resource ('worksheets associated with the workbook') but uses the passive verb 'Represents' instead of active verbs like 'Lists' or 'Retrieves'. It adequately identifies the scope but lacks clarity on the action being performed, requiring inference from the tool name.

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 tool versus related Excel siblings like 'get-excel-range' or workflow prerequisites (e.g., that driveId/driveItemId must be obtained from 'list-folder-files' or 'get-drive-root-item'). The description stands isolated without contextual usage hints.

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