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. The description adds minimal behavioral context beyond confirming the read operation, failing to explain OData filtering capabilities, pagination behavior (despite fetchAllPages parameter), or response structure.

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 is efficient, but 'from the tasks navigation property' is verbose technical cruft that adds no actionable meaning for tool selection. Front-loading is acceptable but jargon reduces clarity per word.

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 12 parameters including complex OData options and no output schema, the description is minimal but technically sufficient given strong schema coverage. However, it omits functionally important context like 'use filter parameter to narrow large task lists'.

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 the baseline is 3. The description mentions 'specified todoTaskList' which loosely maps to the required todoTaskListId parameter but adds no semantic value for the 11 optional OData query parameters (filter, expand, etc.).

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 states the action (Get) and resource (todoTask resources) but obscures clarity with Graph API jargon ('navigation property'). It fails to distinguish from sibling 'get-todo-task' (likely single-item retrieval) or clarify that this returns a collection.

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?

Provides no guidance on when to use this versus 'get-todo-task' for retrieving a specific task, nor when to use 'list-todo-task-lists' to find the list ID first. No prerequisites or filtering recommendations are mentioned despite 12 query parameters being available.

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