Mark a Microsoft To Do task as completed using its task ID, or find it by title and list name when no ID is available.
把任务标记为已完成（勾选）
| Name | Required | Description | Default |
|---|---|---|---|
| list | No | 限定在某个列表中查找 | |
| title | No | 任务标题（支持部分匹配） | |
| taskId | No | 任务 id（优先于 title） |
Changes observed during successful MCP inspections.
v0.2.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
注解已说明它不是只读也不会破坏数据，但描述没有添加任何关于认证需求、任务匹配模糊时如何处理，或是否依赖于某个列表或标题/ ID 解析顺序的信息。
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?
单个简洁的句子，没有冗余，但过于简短，无法承载有用的使用指南。
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?
对于包含 3 个可选参数且没有输出架构的变更工具而言，描述过于单薄；解释了任务匹配方式或如何在同级工具之间选择等基本调用细节都缺失。
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?
架构描述覆盖率为 100%，因此所有参数及其语义（列表、标题、taskId 且 taskId 优先）都已在架构中说明。描述没有提供额外细节；当架构承担主要说明时，基准分为 3 是合适的。
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?
明确的动词+资源（把任务标记为已完成），并且与存在的同级工具 uncomplete_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?
没有说明何时使用此工具而非其他工具、没有任何前置条件，或如何传入任务标识符。
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.