Task Delete Tool

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. The statement 'This cannot be undone' clearly warns about irreversibility, which is the key behavioral trait for a delete operation. It does not mention permissions or side effects, but the explicit permanence warning is a meaningful disclosure.

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 extremely concise: two short sentences with no filler. The primary action is front-loaded, and the critical irreversibility warning is placed immediately after, making the structure efficient and easy to parse.

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 one-parameter delete tool with an output schema, the description is nearly complete. It clearly states the action and the permanence of the operation. It doesn't mention what happens if the task doesn't exist or whether there are cascading effects, but those details are likely covered by the output schema and are not essential for basic invocation.

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 schema has 100% description coverage for the only parameter, task_id, which is documented as 'The task ID to delete.' The description adds no additional parameter semantics, so the baseline score of 3 is appropriate since the schema already fully explains the parameter.

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 uses a specific verb and resource ('Delete a task') and is unambiguous about what the tool does. It doesn't explicitly contrast with sibling tools like task_complete_tool or task_undo_tool, but the delete operation is distinct enough that an agent can recognize its purpose.

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 when to use the tool: when a task needs to be permanently removed. However, it gives no explicit guidance about when not to use it or alternatives, such as completing or undoing a task instead. For a simple destructive operation this is adequate but not thorough.

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