harvest_delete_time_entryPermanently delete a time entry by id. This cannot be undone. Harvest REST: DELETE /time_entries/{id}. WRITE — destroys data.
| Name | Required | Description | Default |
|---|---|---|---|
| time_entry_id | Yes | The time entry id to delete (required). |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations include destructiveHint=true, and the description reinforces this with 'cannot be undone' and 'destroys data', adding permanence context beyond the simple destructive flag. Also mentions the REST endpoint and WRITE nature, which is useful but not required.
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?
Four short sentences, each earning its place: purpose, irreversibility, REST endpoint, and side-effect class. No fluff, front-loaded with the core action.
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 one-parameter delete operation, the description covers action, irreversibility, API method, and write nature. It doesn't explain error handling or prerequisites, but for this simple tool with no output schema, the description is sufficiently 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 has 100% coverage with a clear description for time_entry_id. The description only says 'by id' and adds no additional parameter semantics, so it relies on the schema – baseline 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?
States the specific action: 'Permanently delete a time entry by id' – a clear verb+resource combination. The description distinguishes this from sibling tools like update, stop, or restart by emphasizing deletion and 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?
Implies usage (delete the entry you want removed), but does not explicitly state when not to use it or compare to alternatives. Given siblings like harvest_stop_time_entry, an explicit exclusion (e.g., 'to stop a running timer, use stop_time_entry instead') would improve guidance, but the irreversible nature is a clear signal.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.