Delete task list

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

Annotations already declare destructiveHint and readOnlyHint false, but the description adds valuable context: it deletes all tasks in the list, is permanent, and requires confirm=true. This goes beyond the safety flags and explains the operational impact, making behavior clear.

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 sentences, front-loaded with the primary action and consequence, and zero redundancy. Every phrase earns its place: the destructive scope, irreversibility, and required guard.

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?

Given the simplicity of the tool (2 required params, no output schema, no nested objects) and strong annotations (destructiveHint, readOnlyHint), the description covers all essential behavioral information: what gets deleted, permanence, and the confirm requirement. Nothing critical is missing.

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% for both parameters, so the description's mention of 'confirm=true' adds little beyond what the schema already states. It does not introduce new parameter semantics or clarify usage beyond the schema.

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 uses a specific verb+resource ('Permanently delete a task list') and clarifies the scope ('and every task in it'), distinguishing it from sibling tools like delete_task and clear_completed. It also conveys the permanence and the required confirm flag, leaving no ambiguity about its function.

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?

Usage context is implied: this is for permanent deletion of a list and its tasks, and the description notes it cannot be undone. However, it does not explicitly say when to use this versus alternatives like delete_task or clear_completed, nor does it mention any exclusions or prerequisites beyond confirm=true.

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