Delete a specific task permanently from Teamleader Focus CRM using its ID. This action cannot be undone.
Delete a task. This is irreversible.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | The task ID to delete |
Changes observed during successful MCP inspections.
v1.0.2Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotation destructiveHint=true already signals destructiveness. The description adds the 'irreversible' warning, which reinforces the behavioral profile but does not disclose additional side effects, permissions, or cascading consequences.
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 two short sentences with no filler. The core action is stated first, and the irreversible warning is a meaningful addition that earns its place.
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 simple single-parameter delete operation with a destructiveHint annotation, the description is nearly complete. It could mention potential side effects on related data, but the essential context for calling the tool correctly is present.
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 schema covers the only parameter 'id' with a clear description. The tool description adds no extra semantic meaning beyond the schema, so the baseline score of 3 is appropriate.
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 states a specific verb ('Delete') and resource ('a task'), making the tool's purpose unambiguous. It is clearly distinct from sibling tools like teamleader_update_task, teamleader_complete_task, and teamleader_schedule_task.
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 implies usage: use this when a task needs to be deleted. However, it does not explicitly contrast with alternatives or state when not to use it, leaving some guidance to inference.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.