Microsoft 365 MCP Server

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

Annotations provide readOnlyHint=true, openWorldHint=true, and destructiveHint=false, covering safety and scope. The description adds 'Read-only', which aligns with annotations but is redundant. It also mentions 'Navigation property', which is vague but hints at relational data. However, it fails to disclose pagination behavior (implied by top/skip parameters), rate limits, or authentication needs, leaving gaps despite annotations.

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 description is concise (one sentence) but under-specified. 'The events in the calendar' is front-loaded but vague, and 'Navigation property. Read-only.' adds minor context without earning its place. It lacks structure to guide the agent effectively, making it minimally adequate but not helpful.

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?

Given 13 parameters, no output schema, and annotations covering only safety/scope, the description is incomplete. It doesn't explain the tool's purpose relative to siblings, how parameters interact, or what the output looks like (e.g., event list format). For a complex listing tool with many filtering options, this leaves significant gaps for agent understanding.

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 description coverage is 100%, so parameters are well-documented in the schema. The description adds no parameter-specific information beyond what the schema provides. It doesn't explain how parameters like 'calendarId' or 'timezone' affect the operation, nor does it clarify the relationship between parameters (e.g., pagination with top/skip). Baseline 3 is appropriate given high schema coverage.

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 events in the calendar. Navigation property. Read-only.' is vague and tautological. It essentially restates the tool name ('list-specific-calendar-events' becomes 'events in the calendar') without specifying the action clearly. While 'Read-only' adds some context, it doesn't distinguish this tool from its sibling 'list-calendar-events' or explain what 'specific' means (likely filtering by calendarId).

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?

There is no guidance on when to use this tool versus alternatives. The description does not mention the sibling tool 'list-calendar-events' or clarify that this tool is for events in a specific calendar (implied by the required calendarId parameter). Without explicit when-to-use instructions, the agent lacks context for tool selection.

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