Delete ticket time entry

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is known. The description adds no behavioral context of its own — nothing about irreversibility, what happens to the parent ticket's totals, or re-deletion behavior — so it contributes nothing beyond structured data.

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?

A single short sentence that is front-loaded and waste-free, but this is under-specification rather than true conciseness. Nothing in the sentence earns more value than the tool name already conveys.

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?

With an output schema present, rich annotations, and 100% parameter coverage, the structural gaps are covered elsewhere, so the description need not explain return values. However, for a destructive operation, it says nothing about irreversibility or failure conditions, leaving a meaningful behavioral gap.

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%, with both ticket_id and time_entry_id documented as integers in the schema, so the baseline of 3 applies. The description adds no meaning beyond the schema, such as the relationship between the two IDs.

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 and resource (delete a time entry on a ticket), which is clear but essentially restates the tool name and title without expanding on scope. It makes no attempt to distinguish this from siblings like update_ticket_time_entry or view_ticket_time_entry beyond the word 'delete'.

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 about when to use this tool versus the sibling time-entry tools (list, view, create, update), nor any stated preconditions such as required permissions or whether the entry must belong to the given ticket. The agent must infer all usage context.

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