delete_list

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

It discloses destructive consequences beyond the annotations: cascading deletion of every task, no recycle bin or recovery path, and the requirement to confirm with the user. This goes well beyond the destructiveHint and openWorldHint annotations and does not contradict them.

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 short sentences front-load the critical consequences ('permanently delete', 'no recycle bin') before the user-confirmation note. Every clause earns its place without 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?

With a one-parameter schema fully described, no output schema, and annotations covering the safety profile, the description supplies all needed operational context: what is destroyed, irreversibility, and the confirmation step. Nothing necessary for calling it correctly 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 coverage is 100% and fully documents the single required 'list' parameter, so the description is not responsible for explaining parameters. It adds no param-specific meaning, earning the baseline 3 for fully-covered schemas.

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 states a specific verb ('delete'), resource ('To Do list'), and scope ('every task in it'), making it clearly distinct from sibling tools like delete_task. The permanence qualifier removes any ambiguity about the operation.

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 clearly establishes when to use the tool: to permanently delete a list after user confirmation. It doesn't explicitly name alternatives or when-not-to-use conditions, but the sibling list and task tools make the distinction straightforward.

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