delete_task

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

No annotations are provided, so the description carries the full burden. It adds context about completed tasks auto-archiving, which helps clarify the lifecycle. However, it does not disclose whether deletion is permanent, what happens to associated data, or any prerequisites/effects beyond the act of removal. This is a gap for a destructive operation with no annotation support.

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, front-loaded with the core purpose and followed by a relevant contextual note. It contains no redundant filler and every sentence contributes meaningful guidance.

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 no output schema, the description covers the main purpose and usage conditions (cancelled/mistaken vs completed). It could be more complete by stating whether deletion is permanent or if there are side effects, but overall it adequately orients the agent for the tool's scope.

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 100% coverage for the single parameter (task_id) with a clear description. The tool description adds no additional information about the parameter beyond re-stating the purpose, so the baseline of 3 applies.

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 ('Remove') and resource ('task'), clearly scoped to 'cancelled or mistaken' tasks. It distinguishes itself from siblings like update_task, create_task, and remove_milestone by making the deletion purpose explicit and different from other task-related operations.

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?

It explicitly states when to use the tool (for cancelled or mistaken tasks) and when not (completed tasks auto-archive after 7 days, so no need to delete them). While it doesn't name an alternative tool, the auto-archive guidance serves as an alternative path, making the usage context clear.

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