Delete task list

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

Beyond the annotations (destructiveHint=true, readOnlyHint=false), the description adds crucial behavioral detail: 'Permanently delete' and 'Irreversible' emphasize the permanence, while 'AND every task in it' reveals the cascading deletion of all contained tasks. This significantly enriches the safety understanding beyond the annotation alone.

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 three short, impactful sentences. It front-loads the action, then immediately follows with critical warnings ('Irreversible') and a requirement ('Requires confirm=true'). Every word earns its place with no filler or 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 description covers all essential behavioral aspects: permanence, cascading deletion, and the confirmation requirement. There is no output schema, so return values are not expected. The only minor gap is the lack of explicit differentiation from clear_completed, but overall the description is sufficient for a simple destructive tool.

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?

The input schema already provides 100% coverage with detailed descriptions for both list (id or exact title) and confirm (const true). The description's mention of 'requires confirm=true' adds no new information beyond what the schema already states, so the baseline score of 3 is appropriate.

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 clearly states 'Permanently delete a task list AND every task in it,' specifying the exact resource and scope. This distinguishes it from sibling tools like delete_task, which removes only a single task, and clear_completed, which removes only completed items.

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 provides important context: it deletes the list and all tasks, and requires confirm=true. However, it does not explicitly mention when to use this tool versus alternatives like delete_task or clear_completed, leaving usage boundaries implied rather than stated.

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