Delete Task

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

Beyond the destructiveHint annotation, the description details irreversible cascading deletion of comments, assignees, tags, attachments, time entries, outcomes, events, relations, subtasks, and clearing of experiment/insight/meeting links. It also discloses the return value (deleted id), providing essential safety context. No contradiction with annotations.

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?

Compact three-sentence description, front-loaded with the critical permanence warning. Every sentence earns its place—irreversibility, cascading effects, and usage alternatives—with no wasted words.

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 mutation tool, the description covers preconditions (resolve id, confirm), cascading effects, and return value despite lacking an output schema. The rich annotations and schema complement this well, making it effectively 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?

Schema coverage is 100%, so baseline is 3. The description adds value by telling how to obtain the id (via list_tasks) and emphasizing the need for confirmation, which complements the schema's confirm parameter description. This slight extra guidance justifies a 4.

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 delete a task and return the deleted id,' giving a specific verb, resource, and outcome. It clearly distinguishes itself from siblings like update_task and list_tasks by emphasizing irreversibility and deletion scope.

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 instructs to resolve the id via list_tasks and confirm intent first, and recommends update_task as a safer alternative when only removing from the active board. This provides clear when-to-use and when-not-to-use guidance with a named alternative.

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