Delete a time-tracking entry from Teamleader Focus by its ID. Use this to remove incorrect or obsolete time entries permanently.
Delete a time-tracking entry. This is irreversible.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | The time tracking entry 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 a destructive operation, and the description adds the important behavioral detail that the deletion is irreversible. This goes beyond the annotation and sets correct expectations without over-explaining.
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 short sentences, zero filler. The core action is front-loaded, and the irreversibility warning 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?
This is a single-parameter destructive operation with aligned annotations. The description plus schema fully equips an agent to invoke it correctly; no return format or additional context is essential here.
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 description coverage is 100%, and the single required parameter 'id' is already clearly described as 'The time tracking entry ID to delete'. The description adds no new parameter meaning, so the baseline score of 3 applies.
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 names a specific action ('Delete') and a specific resource ('a time-tracking entry'), which clearly distinguishes this tool from sibling delete tools and from the add/update/list time-tracking tools. The purpose is unambiguous.
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?
There is no guidance on when to use this tool as opposed to alternatives like teamleader_update_time_tracking or teamleader_add_time_tracking. The situation is implied by the delete verb, but no explicit context, exclusions, or alternatives are provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.