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

Annotations already flag destructiveHint=true, but the description adds information the annotations cannot carry: the deletion cascades to all contained tasks and there is no recycle bin, so the data is permanently unrecoverable. It also specifies a required confirmation step before invocation, which is exactly the kind of behavioral context an agent needs for a destructive 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?

Three short sentences: action first, then the destructive consequence as a capitalized warning, then the required confirmation. Nothing is wasted and the most important/surprising fact (irreversible cascade) 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?

For a destructive, no-output-schema tool this covers what is destroyed, that it is irreversible, and that user confirmation is required — the core behavioral burden. The only meaningful gap is not telling the agent how to source the listId parameter.

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 description names no parameters at all. 'mailbox' is well documented in the schema including the list_authorized_mailboxes resolution path, but 'listId' has no schema description and the description offers no hint about where to obtain it (e.g., list_outlook_task_lists). At 50% schema coverage the description fails to compensate for the undocumented identifier.

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?

States a specific verb and resource ('Delete a To Do list') and immediately clarifies scope by noting it removes every task inside the list, which separates it from delete_outlook_task (single task) and delete_outlook_task_list vs. the Google counterpart. An agent knows exactly what is affected without opening the schema.

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?

Gives a concrete operational precondition — 'Ask the user to confirm before calling this' — which is real usage guidance for a destructive operation. It does not name an alternative (e.g., delete_outlook_task for removing individual items), so it stops short of explicit when-not routing.

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