Microsoft 365 MCP Server

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

The 'Read-only' statement merely duplicates the readOnlyHint annotation. 'Navigation property' appears to be irrelevant implementation jargon from Microsoft Graph API documentation that provides no behavioral value. No disclosure of pagination behavior, error conditions, or response format despite complex options like fetchAllPages and excludeResponse.

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?

While brief (three fragments), the structure is poor—'Navigation property' wastes space with API implementation detail irrelevant to tool selection, and 'The events in the calendar' is grammatically incomplete. Not front-loaded with the essential action/purpose.

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 9-parameter tool with complex pagination, timezone handling, and OData query options (select/expand), the description is inadequate. No output schema exists, yet the description fails to explain return values, leaving significant behavioral gaps.

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% (all 9 parameters have descriptions), establishing a baseline of 3. The description text adds no parameter-specific context, examples, or usage notes beyond what the schema already provides.

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' is a noun phrase that fails to specify the action (retrieve/fetch) or distinguish from siblings like get-calendar-event or list-specific-calendar-events. It does not clarify that this retrieves a single specific event by ID versus listing multiple events.

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-specific-calendar-events (which lists multiple) or get-calendar-event. No mention of required parameters (calendarId, eventId) or prerequisites in the description text.

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