Microsoft 365 MCP Server

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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. The description mentions 'and their properties' which loosely hints at the select/expand parameters, but provides no details on pagination behavior, OData query syntax, or the return format.

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 a single 11-word sentence with no redundancy. While efficient, it is arguably under-communicating given the 11-parameter complexity. The phrase 'and their properties' earns its place by hinting at projection capabilities.

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 an 11-parameter tool with complex OData-style querying (filter, select, expand, orderby), the description is inadequate. With no output schema provided, the description should explain what constitutes a 'todoTaskList' and how it relates to tasks, or clarify the OData query pattern. It does neither.

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%, establishing a baseline of 3. The description mentions 'properties' which indirectly references the select/expand capabilities, but provides no parameter-specific guidance, examples, or syntax details 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 uses a specific verb 'Get' and identifies the resource as 'todoTaskList objects', distinguishing it from sibling 'list-todo-tasks' (which lists individual tasks). However, it relies on API jargon ('todoTaskList objects') rather than plain language explaining these are task list containers.

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 siblings, nor does it mention prerequisite steps (e.g., selecting an account) or that task list IDs are required to subsequently call list-todo-tasks.

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