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. It does disclose the important behavior that downloaded files are only deleted when force is true, which is valuable. However, it does not mention that deletion is irreversible, what happens to an actively running task, or what occurs to the downloaded files in the default case beyond leaving them intact.

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 compact, front-loaded one-liner followed by a minimal two-item Args block. There is no filler or redundancy; every sentence contributes either purpose or parameter meaning.

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 two-parameter delete tool, the core functional surface is covered, and an output schema exists to handle return values. The main gap is the lack of boundaries against sibling bulk-delete tools and any notes about side effects on active tasks or file permanence, which keeps it from being fully complete.

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?

Schema coverage is 0%, so the description must compensate, and it largely does: task_id is explained as the task to delete, and force is given the meaningful explanation 'Also delete downloaded files' with its default of False. This adds real semantics beyond the schema titles. The task_id explanation is somewhat obvious, so it is not a perfect 5.

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 download task', which gives a specific verb and resource, and the Args section clarifies that it operates on the task identified by task_id. However, it does not explicitly distinguish itself from sibling tools like delete_completed_tasks or delete_done_tasks, so it stops short of 5.

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?

There is no guidance on when to use delete_task versus the sibling batch/cleanup deletion tools. The description does not mention preconditions, such as whether the task must be done or can be running, or when it is preferable to use one of the bulk delete tools. The only usage-adjacent info is the force default, which is more parameter semantics than usage guidance.

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