outlook_delete_task

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

The annotations already declare destructiveHint: true and readOnlyHint: false, so the description does not need to repeat this. The description adds no extra behavioral context such as permanence or cascading effects, but it is consistent with the destructive annotation.

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, concise sentence with no superfluous words. It is well-structured and immediately conveys the tool's purpose.

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 simple delete operation, the description is mostly adequate, but it omits any mention of side effects (e.g., whether the deletion is permanent, whether it affects reminders or subtasks). The optional list_id parameter also raises questions about required context, which are left unanswered.

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?

The schema provides no descriptions for task_id or list_id, and the description does not explain them. While task_id is presumably the identifier of the task to delete, list_id is optional and its purpose is unclear—whether it scopes to a specific task list or is irrelevant is not explained.

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 (delete) and the resource (a task from a Microsoft To Do list). It distinguishes this tool from sibling delete tools by specifying 'task', which is unambiguous.

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 does not explicitly mention when to use this tool over alternatives like outlook_complete_task or outlook_update_task. However, the operation is straightforward and self-explanatory, so some guidance is implicit in the tool name and description.

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