delete_time_entry

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states 'Delete' (a destructive action) but does not mention that deletion is permanent, whether special permissions are required, or what happens to dependent data. This lack of context for a mutation tool is a significant gap.

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, front-loaded sentence with no filler. Every word earns its place: 'Delete a ClickUp time entry.' is concise and direct.

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 simple two-parameter tool with a complete schema, the description is minimally viable but lacks important context: no annotations, no output schema, and no mention of irreversibility or side effects. It adequately states the core action but does not fully cover the operational context expected for a destructive operation.

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 input schema covers 100% of parameters with clear descriptions for team_id and time_entry_id. The tool description adds no parameter-specific meaning beyond the schema, but the schema already provides sufficient semantics. Thus, 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?

The description 'Delete a ClickUp time entry' states a specific verb (delete) and resource (ClickUp time entry), clearly distinguishing it from sibling tools like create_time_entry and get_time_entries. The action is unambiguous and the resource is precise.

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 implies usage: use this tool when you need to delete a time entry. However, it offers no explicit guidance on when not to use it, prerequisites, or alternatives. The context of sibling tools (e.g., create_time_entry, get_time_entries) suggests when deletion is appropriate, but the description itself does not articulate this.

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