delete_time_entry

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

With no annotations, the description carries the full burden of behavioral disclosure. It states the destructive nature implicitly through 'delete' but provides no details on irreversibility, permission requirements, or potential side effects (e.g., related records affected).

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?

The description is a single, compact sentence that immediately conveys the core function. Every word is purposeful, and there is no redundant or filler content.

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?

Given the tool's simplicity (one integer parameter) and the presence of an output schema, the description is minimally adequate. However, it lacks any usage context, such as typical workflow placement or assumptions about existing entries, leaving the agent with only the most basic understanding.

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?

The only parameter, time_entry_id, is referenced by the phrase 'by ID', but this adds no new meaning beyond the schema's property name and type. There is no explanation of how to obtain the ID or any format constraints beyond the integer type.

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 clearly states a specific action ('Delete') on a specific resource ('time entry') and identifies the key identifier ('by ID'). It is unambiguous and distinguishes from sibling tools by resource type.

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?

No guidance is provided on when to use this tool versus alternatives like update_time_entry or log_time. There are no mentions of prerequisites, such as needing to retrieve the time entry first, or scenarios where deletion might be inappropriate.

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