clear_completed_tasks

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. 'Clear' suggests destructive bulk behavior, but the description does not state whether tasks are permanently deleted, what happens to subtasks or list metadata, or how the operation behaves when no completed tasks exist.

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?

A single, front-loaded sentence communicates the action and scope with no filler, repetition, or unnecessary detail. It is efficiently structured for an agent to parse.

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?

With no annotations, no output schema, and no parameter descriptions, the description alone must fully equip an agent to invoke a bulk destructive operation. It leaves ambiguity about whether 'clear' means permanent deletion and does not differentiate this operation from delete_task, creating a meaningful correctness gap.

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 provides no description for tasklist_id, so the phrase 'from a task list' is the only semantic clue that this parameter identifies the list whose completed tasks are cleared. This is useful but minimal; it does not explain requiredness, format, or scope beyond the parameter name.

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 names a specific verb ('Clear'), a specific resource ('all completed tasks'), and a scope ('task list'), which makes the core operation clear. It does not explicitly contrast with sibling delete_task, but the plural 'completed tasks' distinguishes it from single-task 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?

There is no guidance on when to use this tool instead of delete_task, complete_task, or reopen_task, and no mention of prerequisites or cautions for a bulk operation. The intended use is only implied by the action phrase rather than explicitly stated.

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