everhour_delete_task

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

The description discloses that the action cannot be undone, which is a key behavioral trait. However, with no annotations provided, the description carries the full burden and does not mention other potential side effects such as deleting associated time records or requiring specific permissions. This provides minimal but not comprehensive transparency.

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 composed of two short sentences that are direct and functional. The first states the action, and the second adds an important warning without unnecessary detail.

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 delete tool with one parameter and no output schema, the description covers the core action and irreversibility. However, it does not address potential cascading effects or prerequisites, which could be relevant for an agent. Overall, it is adequate but not exhaustive.

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 the single 'id' parameter with 100% description coverage. The tool description adds no additional meaning about the parameter beyond what is already in the schema, so the baseline of 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 clearly states 'Delete a task from Everhour' with a specific verb and resource. It does not explicitly distinguish from sibling tools like everhour_delete_project, but the tool name and description make the target resource clear. Therefore it is clear but lacks explicit sibling differentiation.

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 the tool's usage by stating it deletes a task, but it gives no guidance on when to prefer this over alternatives or any exclusions. There is no mention of prerequisites or conditions. It is an implied usage with no explicit context.

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