Delete Task

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

Disclosures beyond annotations: irreversible, cascading deletion of subtasks and related entities (comments, assignees, tags, etc.), and clearing of links to experiments/meetings. Consistent with destructiveHint=true and idempotentHint=true.

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 sentences with critical warnings first, then cascade details and alternative. No redundant wording. Front-loaded essential information.

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?

Despite no output schema, description explains return value (deleted id) and fully captures behavioral impact. Covers all key aspects for a destructive tool: irreversibility, cascade scope, and prerequisites.

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%; description adds valuable context that the id comes from list_tasks and is required. This helps the agent understand the provenance and necessity of the parameter.

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?

Clearly states 'PERMANENTLY delete a task and return the deleted id' with specific verb and resource. Distinguishes from sibling tools like update_task by emphasizing permanence.

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 advises to resolve id via list_tasks and confirm intent, and recommends update_task as a safer alternative for non-permanent removal. Provides clear when-to-use and when-not-to-use guidance.

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