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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description adds the non-obvious operational fact that To Do has no recycle bin, i.e. the deletion is unrecoverable. It does not address permissions beyond what the mailbox schema field already hints at (list_authorized_mailboxes), so it falls short of a 5.

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 short sentences, zero filler. The irreversible-deletion warning is front-loaded and the alternative-tool guidance follows immediately.

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?

No output schema exists, and the safety profile is carried by annotations plus the explicit no-recycle-bin warning, so the behavioral story is complete. The remaining gap is the undocumented listId/taskId semantics, which an agent must infer from sibling tools.

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% (mailbox is documented), leaving listId and taskId undocumented in both schema and description. The description adds no meaning at all for the parameters, so it fails to compensate for the coverage gap; an agent gets no help on identifying the target task or list.

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 ("Permanently delete a task") and immediately differentiates the action from the sibling complete_outlook_task by naming that alternative. The word "permanently" also disambiguates it from update/complete operations at a glance.

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 an explicit routing rule: prefer complete_outlook_task, except when the task was created in error. That is a clear when-to-use and when-not-to-use statement with the alternative named, which is exactly the burden this tool should carry.

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