Microsoft 365 MCP Server

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

Description aligns with annotations (readOnlyHint=true, destructiveHint=false) by using 'Retrieve'. However, it fails to elaborate on 'openWorldHint' implications, rate limits, or what specific 'relationships' are available (tasks, buckets, etc.).

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?

Single 9-word sentence with no filler. Front-loaded with action verb. However, extreme brevity leaves significant conceptual gaps unexplored for a 6-parameter OData endpoint.

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?

Mentions 'properties and relationships' hinting at OData capabilities, but lacks output format details, pagination behavior explanations (despite fetchAllPages param), or Microsoft Planner domain context. Adequate but minimal for this complexity level.

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 100%, establishing baseline 3. Description mentions 'properties and relationships' which loosely maps to 'select' and 'expand' parameters, but adds no syntax details, format guidance, or explanations for flags like 'fetchAllPages' or 'excludeResponse'.

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?

States basic purpose with clear verb ('Retrieve') and resource ('plannerplan object'), but fails to distinguish from siblings like 'get-planner-task' or 'list-plan-tasks'. Uses 'plannerplan' as one word while tool name uses 'planner-plan', creating mild confusion.

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 'list-plan-tasks' or prerequisites like requiring a valid plan ID. No discussion of alternatives or selection criteria.

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