delete_task
Delete a specific task from the workflow using its ID to clean up or reconfigure task sequences.
Instructions
Delete a task by ID
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | The ID of the task to delete |
Delete a specific task from the workflow using its ID to clean up or reconfigure task sequences.
Delete a task by ID
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | The ID of the task to delete |
Changes observed during successful MCP inspections.
v1.2.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full burden. Only states 'Delete a task by ID', lacking details on permanence, cascading effects, or required permissions.
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?
Extremely concise single phrase. No wasted words, but could be slightly expanded to improve clarity without losing conciseness.
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 (1 param, no output schema), the description is incomplete. It does not explain behavior like permanent deletion or relationship to subtasks, which is relevant given sibling tools.
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 has 100% coverage for the id parameter with description. Tool description adds no further value beyond the schema's parameter description, meeting baseline.
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?
Verb 'Delete' and resource 'task' are clearly stated. However, no differentiation from sibling tools like clear_all, reset_task, or retry_task, which could overlap in purpose.
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?
No guidance on when to use delete_task versus alternatives. Does not specify prerequisites, such as whether the task exists or if user has permissions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.