delete_task

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

With no annotations, the description carries the behavioral burden. 'Permanently delete' clearly conveys that the action is destructive and irreversible, which is valuable. However, it does not disclose possible side effects, permission requirements, or whether deletion cascades to related resources.

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 a single clear, front-loaded sentence with no wasted words. It is concise and scannable, though it sacrifices useful detail for brevity.

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 destructive two-parameter tool with no annotations and no output schema, the description is incomplete. It provides the core intent and permanence, but lacks usage context and parameter clarification, so an agent does not have enough information to confidently invoke it correctly.

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 0% description coverage and the description provides no explanation of task_id or tasklist_id. The description omits any meaning around the two required identifiers, leaving the agent to guess which ID refers to the task and which refers to the containing task list.

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 verb 'delete' and the resource 'a task,' plus the modifier 'permanently,' making the core purpose unambiguous. It does not explicitly distinguish itself from sibling tools like clear_completed_tasks, but the singular 'a task' signals targeted deletion of one task.

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?

No guidance is provided about when to use this tool versus alternatives such as clear_completed_tasks, update_task, or complete_task. The description does not mention whether tasks must be completed before deletion, what happens to subtasks, or any exclusions.

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