Microsoft 365 MCP Server

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

Annotations indicate readOnlyHint=true, destructiveHint=false, and openWorldHint=true, covering safety and scope. The description adds minimal context by implying it fetches file content, but does not disclose rate limits, authentication needs, or response behavior (e.g., streaming vs. full download). No contradiction with annotations exists.

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 a single vague sentence that fails to convey essential information, making it under-specified rather than concise. It lacks front-loaded clarity and does not efficiently communicate the tool's function or usage.

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 (6 parameters, no output schema) and rich annotations, the description is insufficient. It does not explain return values, error handling, or practical use cases, leaving gaps in understanding how to effectively invoke the tool.

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%, so parameters like 'driveId', 'driveItemId', and options such as 'fetchAllPages' are documented in the schema. The description adds no additional meaning beyond the schema, but since coverage is high, the baseline score of 3 is appropriate.

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 'The content stream, if the item represents a file' is tautological—it restates the tool name 'download-onedrive-file-content' without specifying the action or resource clearly. It fails to distinguish this tool from siblings like 'get-onenote-page-content' or 'upload-file-content', leaving the purpose vague.

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 is provided on when to use this tool versus alternatives. It does not mention prerequisites (e.g., authentication), context for file retrieval, or differences from other content-fetching tools like 'get-mail-attachment' or 'get-onenote-page-content', making usage unclear.

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