delete_task_list

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

Beyond the 'destructiveHint' annotation, the description adds significant behavioral context: it requires the 'exact current title' as a precondition, and it clarifies that the task check includes 'hidden and completed tasks,' which is a crucial operational detail.

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?

Despite the high complexity of the operation, the description is highly efficient. Every sentence is focused on establishing a precondition, a constraint, or a specific behavioral outcome, resulting in zero waste.

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?

Considering this is a high-risk, low-coverage, destructive tool with complex prerequisites (ID matching, title matching, content checks), the description is entirely comprehensive, preventing ambiguous execution paths.

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?

Given the low schema description coverage (25%), the description adds massive value by clarifying the roles of the required parameters (ID vs. title) and detailing the complex logic governing the 'allow_nonempty' flag and user approval flow.

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 purpose is stated clearly: 'Permanently delete a task list.' It is specific and distinguished from sibling tools by specifying the complex content checking behavior required during the deletion process.

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?

It provides crucial usage guidelines by defining the content constraints. It explicitly states that deletion is refused unless 'allow_nonempty=true' is set, providing a clear operational boundary for the agent.

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