Time Delete Time Entry

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

Annotations already declare destructiveHint=true and idempotentHint=false, but the description adds value beyond them: the confirm=True safety gate and a candid warning that the underlying route is undocumented and may be changed or removed without notice. It still does not say whether deletion is recoverable or what happens to an approved/locked entry, which keeps it short of a 5.

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?

Short and front-loaded: the verb+resource and the confirm requirement come first, with the route caveat after. The documented/undocumented route sentence is somewhat implementation-detail heavy but earns its place as a stability warning.

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?

An output schema exists, so return values need no explanation, and the confirm gate plus route risk cover the main behavioral hazards. Still missing for a destructive single-record mutation: accepted `entry_id` formats and any state preconditions (approved, locked, or submitted timesheets) that would cause the delete to fail.

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 0%, so the description must carry the load. It explains the purpose of `confirm` as a destructive-operation gate but says nothing about `entry_id` — notably that it accepts either an integer or a string via anyOf — so only half the parameters gain meaning.

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 a specific verb and resource ('Delete a time entry'), which is unambiguous and clearly a mutation. It does not, however, differentiate itself from the sibling `time_bulk_delete_time_entries`, so an agent must infer that this handles a single entry.

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 states a hard precondition ('requires confirm=True'), which is real usage guidance. It gives no guidance on when to prefer this over `time_bulk_delete_time_entries`, nor any prerequisites such as whether the entry must be unlocked or unapproved before deletion.

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