Microsoft 365 MCP Server

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

While not contradicting annotations (destructiveHint: true aligns with 'Create'), the description adds no behavioral context beyond the single verb. It does not disclose idempotency, required permissions, or side effects beyond what annotations imply.

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?

Extremely concise (single sentence), but undersized for the tool's complexity. The sentence does not earn its place by providing actionable guidance, though it is not verbose or poorly structured.

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?

Inadequate for a complex creation tool with nested objects and destructive annotations. Missing critical context about required relationships (plan/bucket), return behavior, or how to locate created resources.

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?

The description adds no parameter-specific information, but the input schema has 67% description coverage with detailed field descriptions for the complex body object (title, dueDateTime, priority, etc.), meeting minimum viability without descriptive assistance.

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 tautologically restates the tool name with minimal variation ('Create a new plannerTask'). It fails to distinguish from sibling tools like create-todo-task or explain what constitutes a Planner task versus other task types.

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?

Provides no guidance on when to use this tool versus alternatives, prerequisites such as requiring an existing planId/bucketId, or specific contexts where Planner tasks are appropriate.

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