outlook_delete_checklist_item

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the agent knows this is a destructive write. The description restates the deletion but adds no extra behavioral context, such as whether the operation is reversible, what permissions are required, or what happens to the parent task.

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 wasted words. It is appropriately sized for a simple deletion tool.

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 mutation with three parameters, no output schema, and 0% schema description coverage, the description is too thin. It should at least clarify the required identifiers or the effect of the deletion, even if annotations cover the safety profile.

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 description must compensate for all three parameters. It implies that a 'To Do task' and 'checklist item' are involved, but it does not explain the required task_id/checklist_item_id or the optional list_id, nor does it clarify identifier formats.

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 action ('Delete') on a specific resource ('checklist item') within a specific context ('a To Do task'). It also implicitly distinguishes itself from sibling tools such as outlook_add_checklist_item and outlook_update_checklist_item, which operate on the same resource.

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 guidance on when to use this tool versus alternatives like outlook_update_checklist_item, outlook_delete_task, or outlook_complete_task. It also omits prerequisites or conditions, such as whether the task must be open or whether ownership is required.

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