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

No annotations are provided, so the description carries the burden of disclosing the destructive nature of the operation. It clearly states that the deletion is permanent and that To Do has no recycle bin, which is the critical behavioral fact an agent needs before calling this tool.

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 compact sentences deliver the action, the consequence, and the preferred alternative. There is no filler, and the most important fact — permanent deletion — is front-loaded.

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?

The tool's purpose and irreversibility are well covered, but the description does not tell an agent how to obtain the required listId and taskId, and there is no output schema to clarify the return value. For a destructive tool with three required parameters, this leaves a gap in operational completeness.

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 only 33%, and the description adds no parameter-level meaning. The mailbox parameter is documented in the schema, but listId and taskId are left as bare strings with no explanation of where they come from or how they relate to Outlook task lists and tasks.

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 precise action ('Permanently delete a task') on a specific resource, immediately clarifying that this is not a reversible or soft-delete operation. It also distinguishes itself from complete_outlook_task, which is the closest sibling, by framing deletion as the exception.

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 explicit routing guidance: prefer complete_outlook_task unless the task was created in error. This tells an agent both when to avoid this tool and the condition under which deletion is appropriate.

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