clickup_delete_checklist

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

Annotations mark as destructive and idempotent. Description adds that the deletion is permanent, returns a confirmation string, and clarifies that a 404 means the checklist may already be deleted. This complements the annotations without contradiction.

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-organized with clear sections (main action, when to use, when not, returns, error handling). It is efficient but could be slightly more concise without losing clarity.

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?

Given the tool's simplicity (one parameter, destructive, idempotent), the description fully covers purpose, usage guidelines, return value, and error handling. The existence of an output schema reduces the need to detail return values.

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 `checklist_id` has a schema description ('ID of the checklist to delete'). The description text does not add any additional semantic detail beyond the schema, so baseline 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 opens with 'Permanently remove a checklist (and all of its items) from its task,' clearly stating the verb, resource, and scope. This distinguishes it from siblings like `clickup_delete_checklist_item`.

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 states when to use ('The checklist is no longer needed') and when not to use ('To remove a single item, use `clickup_delete_checklist_item` instead'). Also includes error handling context for 404.

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