clickup_list_delete

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

Describes destructive, irreversible, cascading nature and return value. No annotations, so description carries burden; missing authentication/rate limits but otherwise thorough.

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 sentences front-load action and consequence, then provide usage guidance. No wasted words.

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?

Covers purpose, side effects, return value, and alternatives. Complete for a single-parameter destructive tool.

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?

Single parameter list_id described in schema (100% coverage); description adds context that all tasks inside are deleted with 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?

Clearly states it permanently deletes a ClickUp list with all tasks, comments, checklists, and attachments. Distinct from siblings like clickup_list_update and clickup_task_move.

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 advises to confirm with user before calling and provides alternatives: move tasks with clickup_task_move or use clickup_list_update to rename/archive.

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