tasks_delete

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

With no annotations provided, the description carries the burden of behavioral disclosure. The word 'permanently' conveys irreversibility, which is a key behavioral trait for a delete operation. However, it does not disclose potential side effects (e.g., deletion of subtasks or comments), permission requirements, or behavior on failure, leaving some gaps.

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 a single, concise sentence that is front-loaded with the action. It contains zero redundant words and immediately conveys the tool's purpose, making it 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?

Given the tool's simplicity (one parameter, no output schema, no nested objects), the description is largely complete. It states the core operation and permanence, which is sufficient for a straightforward delete. However, it could be slightly more complete by mentioning when to use it or that it is irreversible in stronger terms, but for this low complexity, the essentials are covered.

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 fully documents the task_id parameter (100% coverage), so the baseline is 3. The description adds no additional context about the parameter, such as how to retrieve a valid task ID or format expectations, but it also does not need to since the schema describes 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?

The description 'Delete a ClickUp task permanently' clearly states the action (delete) and the resource (a ClickUp task), with the adverb 'permanently' adding important nuance. It distinguishes this tool from siblings like tasks_create and tasks_update by specifying the exact operation.

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 no guidance on when to use this tool versus alternatives. There is no mention of scenarios like removing obsolete tasks, nor any exclusions or preconditions. Sibling tools like tasks_update are not referenced, leaving the agent without comparison guidance.

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