clickup_checklist_delete

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively communicates critical behavioral traits: the destructive nature ('permanently delete', 'destructive and irreversible'), the scope of deletion ('including all its items'), and the return value ('Returns an empty object on success'). This covers the essential behavioral aspects for a deletion tool.

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 perfectly concise with three sentences that each earn their place: states the action and scope, warns about destructiveness and provides alternative, and specifies the return value. No wasted words, and the most critical information ('permanently delete', 'destructive') is front-loaded.

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 destructive deletion tool with no annotations and no output schema, the description does an excellent job covering the essential context: purpose, destructiveness warning, alternative tool, and return value. The only minor gap is that it doesn't mention authentication requirements or potential error cases, but given the tool's simplicity (one parameter) and clear behavioral disclosure, it's nearly complete.

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 description coverage is 100%, with the checklist_id parameter already well-documented in the schema. The description doesn't add any additional parameter information beyond what's in the schema, so it meets the baseline of 3 where the schema does the heavy lifting.

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 specific action ('permanently delete'), the resource ('an entire checklist from a ClickUp task'), and the scope ('including all its items'). It explicitly distinguishes from the sibling tool 'clickup_checklist_delete_item' for single-item deletion, providing clear differentiation.

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 provides explicit guidance on when to use this tool ('to remove a single item instead, use clickup_checklist_delete_item') and includes strong warnings about its destructive nature ('destructive and irreversible'), which helps the agent understand when this tool is appropriate versus alternatives.

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