clickup_delete_list

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

Annotations already set `destructiveHint: true`, `readOnlyHint: false`, `idempotentHint: true`. The description adds that deletion is permanent, there is no undo via API, and it removes the List and all its Tasks. It also explains the 404 error condition. This provides meaningful context beyond the annotations.

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 well-structured with clear sections: main action, consequences, usage guidance, returns, example, and error handling. Every sentence adds value and is front-loaded with the essential purpose. It is appropriately sized for the tool's complexity.

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?

Despite the tool being destructive and having a single parameter, the description covers all necessary aspects: purpose, usage guidelines, behavioral transparency, error handling, and an example. It is self-contained and adequately prepares the AI agent for correct invocation, even without output schema content visible.

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 only parameter is `list_id`. The input schema already has a description: 'List id to permanently delete.' The description provides an example usage with a placeholder value, which aids understanding. However, it does not add extra semantic guidance beyond what the schema offers. Given the schema coverage is 0% (likely meaning no tool-level description in schema), the example compensates well, earning a 4.

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 'Permanently delete a List from the Workspace.' It specifies the resource (List) and action (delete), and distinguishes from sibling tools like `clickup_update_list` which is for archiving. This is a specific verb+resource that leaves no ambiguity.

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 explicitly includes 'When to Use' and 'When NOT to Use' sections, advising to permanently delete and to archive instead for temporary hiding, naming the alternative tool `clickup_update_list`. It also recommends confirming with the caller before production use.

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