todo_delete_list

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

With no annotations provided, the description carries the full behavioral burden, yet it only says 'Delete'. It does not disclose whether deletion is permanent, whether contained tasks are also removed, what permissions are required, or whether the operation can be undone — critical details for a destructive operation.

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?

A single short sentence with zero filler and the key verb front-loaded. Its brevity is not the problem; the missing information is captured in the other dimensions.

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 tool with no annotations and an undocumented parameter, the description is too thin. The presence of an output schema reduces the need to explain return values, but the description still fails to cover permissions, cascading effects, and parameter sourcing.

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 0%, so the description carries full responsibility for explaining list_id, but it says nothing about it. An agent cannot tell whether list_id is a GUID, a display name, or how to obtain it (e.g., from todo_list_lists).

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 specific verb and resource ('Delete a To Do list'), which clearly distinguishes it from sibling tools like todo_delete_task and todo_delete_checklist_item. It stops short of naming those siblings, but the resource scope is unambiguous.

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?

There is no guidance on when to use this versus todo_update_list, todo_delete_task, or other siblings, and no prerequisites or confirmation requirements are mentioned. The agent must infer usage entirely from the name and one-line description.

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