delete_timer

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

Annotations already declare destructiveHint=true, but the description adds critical context: the record is gone (hard delete), API returns empty body, and the timer id is invalidated. It also details failure modes (404 for invalid/owned ids). This far exceeds the annotations.

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?

Three paragraphs with clear structure: purpose, behavioral contrast, return value, failure modes, and suggestion. Every sentence adds value, no fluff. Front-loaded with main action.

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?

The tool is simple (one param, no nested objects, empty output). Description covers purpose, behavior, return, failure modes, and gives a remedial suggestion. Complete and self-contained.

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 has one parameter (timer_id) with no schema description, so the description must compensate. It provides context about valid ids (belongs to user, not previously deleted) and failure modes, but does not explicitly describe the parameter's purpose. Given only one parameter, this is sufficient.

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 the tool deletes a time tracker entirely, using specific verbs and resource. It distinguishes from subtask deletion (hard vs soft) and provides use case (cancel a mistakenly started one).

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 explains when to use (delete a time tracker) and contrasts with subtask deletion. It also advises using list_my_timers to confirm ids before retrying, providing usage guidance. However, it does not explicitly mention when not to use or alternatives.

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