delete_task_list

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

With no annotations, the description carries the full burden of behavioral disclosure. It explicitly states 'Irreversible' and that the operation deletes 'its tasks', revealing the permanent, cascading nature of the action. This is meaningful context, though it omits permission requirements and response behavior.

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, front-loaded with the action and target, with 'Irreversible' as a separate high-impact warning. Every word earns its place and there is no redundancy.

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 definition covers the core destructive behavior and irreversibility, and the schema documents the provider parameter. However, it lacks guidance on how to obtain valid listId values and does not situate the tool relative to delete_task or move_task_between_lists. For low complexity and no output schema, this is a moderate gap.

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 50%: the required listId has no description in the schema, and the tool description does not compensate. Provider is documented, but listId's format, meaning, and source are never explained. The description adds no parameter-level semantics.

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?

Description uses a specific verb ('Delete') with a clear resource ('entire task list and its tasks'), which distinguishes it from sibling delete_task (single task). It also communicates the cascade scope, making the tool's purpose unmistakable.

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 implies use when wanting to delete a whole list, but it provides no explicit guidance on when to use this tool versus delete_task or move_task_between_lists. It also does not state exclusions or prerequisites, so usage context is only implicit.

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