Microsoft 365 MCP Server

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

The description doesn't contradict the annotations, which already indicate this is a destructive, non-read-only operation with open-world semantics. While the annotations cover the core behavioral traits, the description adds some context by mentioning 'navigation property events,' though this is more confusing than helpful. No additional behavioral details like authentication needs, rate limits, or error conditions are provided.

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 the description is brief (one phrase), it's not effectively concise because it uses confusing terminology ('navigation property events') that doesn't clearly communicate purpose. The structure is poor as it doesn't front-load essential information about what the tool actually does. It's under-specified rather than efficiently concise.

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 destructive tool with no output schema, the description is inadequate. It doesn't explain what happens after deletion, whether the action is reversible, what the response contains, or how it differs from the sibling 'delete-calendar-event' tool. The annotations provide safety information, but the description fails to add necessary context for proper tool selection and invocation.

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?

With 100% schema description coverage, the input schema already documents all 5 parameters thoroughly. The description adds no parameter-specific information beyond what's in the schema. The baseline score of 3 reflects adequate parameter documentation through the schema alone, with no additional value from the description.

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 'Delete navigation property events for me' is vague and confusing. It doesn't clearly state that this tool deletes a specific calendar event, nor does it distinguish it from the sibling 'delete-calendar-event' tool. The phrase 'navigation property events' is technical jargon that doesn't clearly communicate the tool's function to an AI agent.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention the sibling 'delete-calendar-event' tool or explain why this specific version exists. There's no information about prerequisites, context, or when this tool should be selected over other deletion tools.

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