google_tasks_delete_listDelete a Google Tasks list and all its tasks using a task list ID. Removes the selected list from the specified Google account.
Delete a Google Tasks list (removes its tasks).
| Name | Required | Description | Default |
|---|---|---|---|
| account | No | Account nickname to use. | |
| tasklistId | Yes | Task list ID. |
Changes observed during successful MCP inspections.
v0.1.60Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It partially conveys destructive behavior by saying 'Delete... (removes its tasks)', which hints at the cascade effect—a useful behavioral detail. However, it omits critical information such as whether the list can be recovered, what permissions are required, or what happens to shared lists.
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, efficient sentence that front-loads the action and resource. It is appropriately sized, though it could be slightly more informative without becoming verbose.
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 mutation tool with no annotations, no output schema, and only two parameters, the description is insufficiently complete. It doesn't clarify required permissions, irreversibility, or how it differs from sibling tools like google_tasks_delete and google_tasks_update_list.
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%, so the schema fully documents both parameters. The description adds no additional parameter meaning beyond what the schema provides. Baseline 3 is appropriate when the schema does the heavy lifting.
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 clear verb 'Delete' and resource 'Google Tasks list', making the purpose understandable. However, it does not distinguish this tool from the sibling google_tasks_delete (which deletes tasks within a list) or google_tasks_update_list, so an agent must infer the distinction.
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?
No when-to-use guidance is provided. The description doesn't mention prerequisites like ownership, required permissions, or the fact that deletion is irreversible. There is no mention of alternatives or when not to use this tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.