todo_delete_list

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

The annotations already mark this as destructive, but the description adds critical behavior beyond them: deletion is permanent, all contained tasks are also deleted, user confirmation is required, and the default list is protected. This is exactly the context an agent needs before invoking a destructive cascade.

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 compact sentences with the destructive scope and safety precondition front-loaded. Every sentence adds actionable information without 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?

For a simple destructive tool with annotations covering safety and no output schema, the description explains the important behavior: permanence, cascading deletion, confirmation, and the default-list exception. The main remaining gap is how list_ref identifies the list, which is a parameter-level omission rather than an overall behavioral omission.

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 schema has one required parameter, list_ref, with 0% description coverage, and the tool description does not explain whether list_ref is a name, ID, or reference format. The mention of the default 'Tasks' list provides slight context but does not compensate for the missing parameter 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?

The description uses a specific verb and resource: permanently delete a To Do list. It also clarifies cascading scope by stating that all tasks in the list are deleted, which distinguishes it from todo_delete_task.

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 gives clear usage guidance: confirm with the user first, and do not use it on the default 'Tasks' list. It does not name an alternative tool, but the when-to-use and when-not-to-use conditions are explicit.

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