Microsoft 365 MCP Server

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

Description confirms write operation ('Create') consistent with destructiveHint=true, but adds no details about return values, side effects, idempotency, or specific behavioral traits beyond what annotations and schema structure provide.

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 efficient sentence with no redundancy. Information is front-loaded and every word contributes to understanding the operation scope.

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?

Adequate for the tool's complexity given high schema coverage and present annotations, but minimal. Lacks guidance on handling the response (no output schema) and explicit prerequisite guidance for obtaining the required list ID.

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 75% schema coverage, baseline is 3. Description adds semantic mapping that 'body' contains the task object and implies 'todoTaskListId' is the target container, but does not elaborate on complex nested body structure or the purpose of optional flags.

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?

Clear verb (Create) and resource (task object) with specific container context (todoTaskList), effectively distinguishing from planner tasks and other creation tools. Lacks explicit Microsoft To Do branding but uses domain-specific terminology.

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 explicit guidance on when to use versus create-planner-task or prerequisite steps (e.g., obtaining todoTaskListId from list-todo-task-lists). While 'specified' implies a required parameter, it does not explain preconditions or sibling alternatives.

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