delete_list

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

With no annotations, the description fully covers key behavioral traits: permanent deletion, irreversibility, and return of confirmation with ID. It could add authorization or rate limit details, but the core destructive nature is transparent.

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?

Three short sentences containing all essential information with zero waste. The main action is front-loaded, and every sentence adds value.

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, the description covers operation, irreversibility, and return type. It could specify the confirmation structure more, but it is sufficiently complete given the tool's simplicity.

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 description does not add extra meaning beyond 'ID of the List to delete.' Baseline 3 is appropriate as the schema already documents the parameter well.

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 the tool deletes a List and all its tasks, using specific verbs and resources. It distinguishes from sibling delete tools like delete_task and delete_folder by specifying the scope (all tasks inside).

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 implies irreversible deletion but does not explicitly compare to alternatives like archiving or moving tasks. It provides clear context for when to use (permanently remove a list) but lacks explicit exclusions or alternative tool references.

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