delete_completed_tasks

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

With no annotations, the description carries the behavioral burden. It correctly discloses that `force` will also delete downloaded files, but it does not mention irreversibility, confirmation behavior, or whether active/incomplete tasks are protected. A deletion tool with no annotation coverage should state these caveats.

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 short, front-loaded with the main action, and includes only the necessary `force` clarification. Every sentence earns its place; there is no redundant filler.

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?

The tool is simple and has an output schema, so return values need not be explained, but the missing distinction from `delete_done_tasks` and the undefined term 'historical' prevent an agent from being fully confident about scope. A sentence clarifying prerequisites or irreversibility would make the definition 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?

The only parameter, `force`, is a bare boolean in the schema with 0% schema description coverage. The description fully compensates by explaining that passing force also deletes the downloaded files for each completed task.

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 states a specific action ('Delete all') and a clear target ('completed historical download tasks'), so an agent can understand what the tool does. However, it does not differentiate from the sibling `delete_done_tasks`, which appears to cover the same or overlapping concept, so it stops short of a 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?

No guidance is given about when to prefer this tool over `delete_task`, `delete_done_tasks`, or any other sibling. The phrase 'completed historical' only implies the selection criteria; it does not state exclusions or point to alternatives.

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