Microsoft 365 MCP Server

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

While annotations correctly mark this as destructive, the description adds no behavioral context about deletion mechanics (permanent vs. recycle bin, concurrency control with If-Match, or what occurs upon success). It merely repeats the technical 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?

The single sentence is terse but inefficient—it uses obscure technical terminology ('navigation property') that obscures rather than clarifies, failing to front-load the actual resource being manipulated (OneDrive files).

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 destructive file operation with 5 parameters and no output schema, the description is inadequate. It omits response behavior, error conditions, and the significance of the ETag parameter for optimistic concurrency.

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, parameters are well-documented in the schema itself. The description mentions neither specific parameters nor their semantics, warranting the baseline score.

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 Graph API jargon ('navigation property items') instead of clear user-oriented language. It fails to explicitly state this deletes files/folders from OneDrive, making it vague despite the clear 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 versus other deletion siblings (delete-mail-attachment, delete-calendar-event, etc.) or prerequisites like required permissions for OneDrive operations.

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