clickup_checklist_delete_item

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

With no annotations provided, the description carries full burden. It clearly conveys destructive nature ('Permanently delete', 'irreversible') and states return value ('Returns the updated checklist object'). It does not cover permissions or rate limits, but for a delete tool, the core behavioral traits are well disclosed.

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 focused sentences: first states action and nature, second provides alternative and return info. No redundant words, highly efficient.

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 delete tool with two well-documented parameters and no output schema, the description is complete. It explains destructive nature, alternative, and return. Could mention error handling or permissions, but given low complexity, it's adequate.

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 input schema already has 100% description coverage, providing clear meaning for both parameters (checklist_id and item_id). The description adds no additional parameter context, but the schema is sufficient. Baseline score of 3 is appropriate.

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 single item from a ClickUp checklist', specifying the exact verb (delete), resource (checklist item), and scope (single item). It differentiates from sibling tool clickup_checklist_update_item by noting that alternative is for resolving without deleting.

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 says 'Destructive and irreversible' to warn when not to use, and provides an alternative: 'To resolve the item (mark done) without deleting, use clickup_checklist_update_item with resolved=true.' This gives clear when-to and when-not-to guidance.

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