Microsoft 365 MCP Server

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

Annotations clearly mark this as read-only and non-destructive. The description adds technical context via the '/calendars navigation property' reference and explains that results can be scoped to calendar groups. Does not address pagination behavior, throttling, or the fact that all parameters are optional OData query options.

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 sentence structure that front-loads the primary action. Slightly repetitive phrasing ('get..., get...') and comma splice structure could be tighter, but no extraneous content or marketing language.

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?

With 11 optional parameters and no output schema, the description covers the basic retrieval purpose but lacks richness expected for a complex OData endpoint. Does not explain common query patterns, pagination (despite fetchAllPages parameter), or response structure.

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 has 100% description coverage for all 11 OData-style parameters (top, skip, filter, etc.). The description adds no parameter-specific guidance, but with comprehensive schema coverage, baseline 3 is appropriate. Description mentions 'specific calendar group' functionality without indicating which parameter controls this.

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 specific verb (Get) and resource (user's calendars) and mentions the underlying Graph API navigation property. Clarifies scope includes default or specific calendar groups. However, does not explicitly distinguish from related siblings like 'list-calendar-events' or 'get-calendar-view', which is important given the dense set of calendar-related tools.

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?

Describes internal variants (all calendars vs specific group) but provides no guidance on when to choose this tool versus the many sibling alternatives (e.g., list-calendar-events vs list-calendars). No mention of prerequisites or constraints.

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