outlook_delete_checklist_item

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

The annotations already declare readOnlyHint=false and destructiveHint=true, so the agent knows this is a destructive write. The description adds the parent context that the item belongs to a To Do task, but it does not explain irreversibility, permission needs, or side effects. With annotations carrying the safety profile, this is minimally adequate.

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 front-loaded sentence with no redundant or filler text. Every word contributes to identifying the action and resource.

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?

This is a destructive three-parameter tool with 0% schema description coverage and no output schema. The description identifies the operation and parent resource but omits parameter guidance, usage context, and behavioral consequences. It is not complete enough for reliable invocation without inspecting the schema manually.

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%, so the schema provides no semantics for task_id, checklist_item_id, or list_id. The description implicitly references task and checklist item, which maps to the two required IDs, but it says nothing about list_id, ID formats, or where those IDs come from. It does not 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?

The description states a specific verb and resource: delete a checklist item from a To Do task. This distinguishes it from deleting an entire task or task attachment. It does not explicitly differentiate from sibling checklist operations, but the resource noun is clear.

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?

The description gives no when-to-use guidance, prerequisites, or alternatives. It does not tell the agent when to delete a checklist item versus updating the task or using a related sibling. Usage is only implied by the operation itself.

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