m365_tasks_delete

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

Annotations already indicate destructiveHint=true and readOnlyHint=false, so the destructive nature is known. However, the description adds no extra behavioral context such as permanence of deletion, cascading effects, or error handling. It does not contradict annotations, but it also does not enrich them.

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, clear sentence with no wasted words. It is front-loaded and readable. However, it is almost too terse, lacking contextual phrases that would make it genuinely helpful, so it earns a 4 rather than a 5.

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 with 2 parameters and rich annotations, the description is minimally viable. It tells the agent the core action, and the schema covers parameters. But it omits information about side effects, permanence, or permissions that would be important for a destructive tool. This is a clear gap, so it gets a middle score.

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 100% — both listId and taskId have clear descriptions. The description 'Delete a task' adds no additional meaning to the parameters, leaving the schema to do the heavy lifting. This aligns with the baseline of 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?

The description 'Delete a task' clearly states the action and resource, using a specific verb ('delete') and noun ('task'). It is unambiguous and distinct from sibling tools like m365_tasks_create or m365_tasks_update, though it lacks explicit scoping or additional detail.

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 provides no guidance on when to use this tool versus alternatives, no prerequisites, and no context about required permissions or conditions. It is essentially the tool's name restated in a sentence, offering no strategic direction for the agent.

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