Delete a checklist item from a Microsoft To Do task after confirming with the user, so task sub-items can be removed accurately.
Delete a checklist item from a To Do task. Confirm with the user first.
| Name | Required | Description | Default |
|---|---|---|---|
| item_id | Yes | ||
| task_id | Yes | ||
| list_ref | Yes |
Changes observed during successful MCP inspections.
v0.2.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered structurally. The description adds the confirmation-before-deletion requirement, which is real added value, but says nothing about irreversibility, whether the parent task is affected, or what is returned.
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?
Two short sentences with zero filler, and the action is front-loaded ahead of the safety instruction. Nothing could be removed without losing information.
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 a destructive three-identifier mutation with no output schema and no parameter documentation, the description is too thin. An agent still cannot determine the format of list_ref or item_id, or how to recover the identifiers needed to call it correctly.
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 0% and all three parameters (list_ref, task_id, item_id) are undocumented bare strings. The description adds no meaning whatsoever about what these identifiers are, their formats, or where they come from, so it fails to compensate for the coverage gap.
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?
States a specific verb and resource: "Delete a checklist item from a To Do task." This distinguishes it implicitly from todo_delete_task (whole task) and todo_update_checklist_item, though it never names those siblings explicitly.
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?
"Confirm with the user first" gives a procedural precondition for invocation, which is genuinely useful. However, there is no guidance on when to choose this over todo_update_checklist_item (e.g. clearing vs removing) or what to do if the item is the last one.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.