Delete task

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

Beyond the annotations (destructiveHint=true), the description adds 'permanent deletion' and 'explicitly confirm', which reveals that the operation is irreversible and requires confirmation. This provides useful behavioral context about the safeguard mechanism, exceeding what annotations alone suggest.

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, front-loaded sentence that captures the essential action and the preview/confirm nuance. Every word contributes value, and it is appropriately sized for the tool's purpose.

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?

The description is adequate for a destructive operation with strong annotations, but it lacks detail on important parameters like confirmation_token and workspace_id, and the absence of an output schema means the return behavior is not described. The preview/confirm workflow is included, but more context on the confirmation mechanism would improve completeness.

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 has zero description coverage, and the tool description does not compensate. It only vaguely hints at the 'preview' and 'confirm' parameters (dry_run and confirm) but does not explain task_id, workspace_id, custom_task_ids, or confirmation_token. An agent would struggle to understand the full parameter semantics from the description alone.

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 tool's purpose: permanently deleting a ClickUp task, with a preview option. It uses a specific verb ('delete' implied by 'permanent deletion') and specifies the resource (ClickUp task). It distinguishes from sibling tools as the only task deletion tool.

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 conveys a clear usage workflow: either preview the deletion or explicitly confirm it. This implies that the tool can be used in a dry-run mode before committing to deletion, offering guidance on the intended two-step process. It doesn't explicitly mention alternatives, but the context is clear enough for an agent.

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