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

Annotations already declare destructiveHint=true, so the bar is lower; the description still adds real value by stating the deletion is permanent and irreversible and by naming the underlying write endpoint (DELETE /time_entries/{id}). It does not discuss auth requirements, error behavior, or restrictions on locked/invoiced entries.

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?

Three short, front-loaded sentences with the destructive consequence stated first. The trailing 'WRITE — destroys data' and the REST path partially restate the destructiveHint, but they cost little and are useful for an agent mapping to the API.

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 single-parameter mutation with destructive annotations and no output schema, the definition covers what the agent must know before calling it. It leaves out failure modes (e.g., entries tied to invoiced time) and any confirmation expectation, which would be the finishing touch.

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?

Only one parameter and schema coverage is 100%, so the schema already documents time_entry_id as a required positive integer. The description's 'by id' adds nothing beyond that, which is the expected baseline when the schema does the heavy lifting.

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 uses a specific verb+resource ('Permanently delete a time entry') and pins the target ('by id'), which cleanly separates it from list/get/create/update/restart/stop siblings in the same namespace. An agent can identify the operation without opening the schema.

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?

It warns that the action is irreversible ('This cannot be undone') but gives no guidance on when to delete versus alternatives such as harvest_stop_time_entry, harvest_restart_time_entry or harvest_update_time_entry. The warning is a caution, not usage routing.

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