Delete Time Tracking Entry

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

Annotations already flag destructiveHint=true, but the description adds important context: 'This cannot be undone' and 'Returns a success message.' This goes beyond the structured annotations, making the irreversibility and output explicit.

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?

Two concise sentences with no wasted words. Each sentence adds value: the action, the irreversibility, and the return result. Front-loaded with the primary purpose.

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 parameter, no output schema, no nested objects), the description fully covers the essential behaviors: what it does, that it's permanent, and what the response looks like. Annotations provide the safety profile. Nothing else is needed.

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 100% and the parameter description is already detailed (GID, numeric string example). The tool description adds no extra parameter semantics beyond the schema, but it does clarify the action's scope ('from a task'), which slightly adds context. 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?

Description clearly states a specific action: 'Permanently delete a time tracking entry from a task.' It uses a specific verb+resource and distinguishes itself from sibling time tracking tools (get/create/update/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?

The description conveys the primary use case: when you want to permanently delete a time tracking entry. It does not explicitly mention alternatives or exclusions, but the context is clear for a delete operation, and the destructive nature is highlighted.

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