delete_task

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. It states that deletion is permanent ('THIS ACTION CANNOT BE UNDONE'), cascades to subtasks ('all its subtasks'), and requires user confirmation. These are the critical behavioral traits an agent must know before invoking a destructive tool.

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 two sentences with no fluff. It front-loads the primary action and unique consequence, then follows with the mandatory confirmation requirement. The all-caps warning earns its place and effectively draws attention to irreversibility.

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 one-parameter delete tool with no output schema and no annotations, this description covers all necessary context: what is deleted, the irreversible nature, and the required pre-step. The agent has everything needed to call the tool correctly and safely.

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 fully documents the single id parameter with 'The task's id.primaryKey' at 100% coverage, so the baseline is 3. The description adds no additional meaning about the parameter beyond what the schema already provides, though it is consistent with the overall purpose.

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 action: 'Permanently delete a task and all its subtasks.' This provides a specific verb (delete), resource (task), and unique scope (subtasks), distinguishing it from sibling tools like complete_task and drop_task by emphasizing permanent deletion. The irreversible nature is immediately communicated.

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 provides an explicit precondition: 'Before calling this tool you MUST ask the user to explicitly confirm...' This tells the agent exactly when the tool is appropriate to call. However, it does not name alternatives such as drop_task or complete_task, so the 'when not to use' dimension is only implicit.

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