Microsoft 365 MCP Server

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

Annotations provide readOnlyHint=true, openWorldHint=true, and destructiveHint=false, covering safety and openness. The description adds minimal behavioral context beyond this, such as implying resource retrieval from a navigation property, but lacks details on rate limits, authentication needs, or response format. No contradiction with annotations exists.

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, efficient sentence that directly states the tool's purpose without redundancy. It's front-loaded with the core action, though it could be slightly more structured by hinting at parameter usage. No wasted words, making it appropriately 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?

Given the tool's moderate complexity (12 parameters, no output schema) and rich annotations, the description is minimally adequate. It covers the basic purpose but lacks guidance on usage, behavioral nuances, or output expectations, leaving gaps that could hinder an AI agent in optimal 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?

Schema description coverage is 100%, with all 12 parameters well-documented in the input schema. The description adds no parameter-specific information beyond implying 'todoTaskListId' is required, which is already clear from the schema. Baseline score of 3 is appropriate as the schema carries the full burden.

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 clearly states the action ('Get') and resource ('todoTask resources'), specifying they come from 'the tasks navigation property of a specified todoTaskList.' It distinguishes from generic list tools by focusing on todo tasks within a specific list, though it doesn't explicitly differentiate from sibling tools like 'list-todo-task-lists' or 'get-todo-task.'

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 is provided on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing a todoTaskListId), compare to 'get-todo-task' for single tasks, or explain when filtering/pagination parameters are useful. The description assumes context without explicit instructions.

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