Delete a task list

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

Goes beyond the destructiveHint annotation by adding crucial behavioral context: no undo, no trash, deletion of every task in the list, rejection of the default list, and the exact return shape. This gives the agent a full picture of the irreversible side effects.

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?

Every sentence earns its place: the action, the irreversibility, the default-list limitation, the alternatives, and the return value are all included without verbosity. The most critical information is front-loaded.

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 single-parameter tool, this description is complete. It covers side effects, edge cases, alternatives, and return value, and the annotations already convey the safety profile. Nothing essential 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%, and the input schema already documents tasklist_id, including the '@default' alias. The tool description itself does not add parameter-level detail, but it also does not need to because the schema fully covers it.

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?

States the specific verb and resource: 'Deletes a task list AND every task in it, permanently.' It clearly distinguishes itself from delete_task and clear_completed_tasks by emphasizing the cascade deletion, so an agent knows exactly what this tool does.

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?

Explicitly explains when to use this tool versus alternatives: if you only need to empty the list but keep it, use clear_completed_tasks or delete tasks one by one. It also warns that the default task list cannot be deleted because the API rejects it.

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