Microsoft 365 MCP Server

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

Annotations correctly indicate this is a non-read-only (write operation), non-destructive action with open-world side effects, but the description adds no behavioral context about overwrite rules, versioning behavior, transactionality, or what 'content stream' implies for the operation.

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 is confusingly fragmented and appears mistakenly copied from a parameter description rather than describing tool behavior. The brevity creates ambiguity rather than clarity, failing to earn its place.

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 an upload operation with openWorldHint=true and no output schema, the description omits critical context about success confirmation, partial upload handling, content-type requirements, and the relationship between the body parameter and the target file.

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 coverage is 80% (body is the only undocumented parameter in the schema). The description provides no explicit parameter mapping, though 'content stream' vaguely alludes to the body payload. With high schema coverage, baseline 3 is appropriate as the description adds minimal semantic value beyond the structured schema.

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' lacks any verb indicating action (e.g., 'uploads', 'writes') and fails to state that this tool transfers data to a file. It reads as a passive data description rather than a functional purpose statement, leaving the agent unable to distinguish this from a download or metadata retrieval tool.

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 siblings like 'download-onedrive-file-content', nor does it clarify prerequisites such as existing file creation or how it handles content replacement versus appending.

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