deleteTimeEntry

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

With no annotations, the description bears full responsibility for behavioral disclosure. It merely states 'delete' without detailing that the action is irreversible, any required permissions, or side effects on linked data. This is insufficient for a destructive operation.

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 terse sentence, which is concise but lacks necessary detail. It is front-loaded but not informative enough given the tool's complexity, making it under-specified rather than appropriately concise.

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 absence of annotations, output schema, and nested parameters, the description fails to provide complete context. It doesn't explain what a time entry is, how to obtain its ID, or the role of the 'format' parameter, leaving gaps for the agent.

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 coverage is 0%, meaning the description adds no parameter information. Although the schema defines 'format' and 'timeEntryId', the description does not explain their purpose or how to use them, requiring the agent to infer from schema alone.

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 time entry' clearly states the action and resource, distinguishing it from other delete tools like deleteIssue. However, it lacks specificity about what constitutes a time entry, though the name itself is fairly clear.

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 such as updateTimeEntry or createTimeEntry. There is no mention of prerequisites like needing a valid time entry ID or the impact on related records.

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