clear_all_tasks

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

The description indicates a destructive action via 'delete' and a confirmation requirement, but it lacks explicit disclosure of irreversibility or side effects. The parameter description (in schema) adds 'irreversible,' but the main description does not.

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 sentence that front-loads the action and includes the confirmation requirement. Every word is purposeful with no redundancy.

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 destructive tool with one parameter and no output schema, the description is fairly complete: it states what it does and the confirmation need. It could mention irreversibility explicitly, but the parameter description covers that.

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 covers the sole parameter 'confirm' with a description of its role. The main description adds that the command requires user confirmation, which is a slight addition. With 100% schema coverage, baseline is 3.

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 specifies 'delete all incomplete tasks,' clearly stating the action and resource. It distinguishes itself from sibling tools like 'delete_task' by targeting all incomplete tasks versus a single 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?

The description explicitly requires user confirmation before execution, providing a clear usage condition. However, it does not contrast with alternatives like 'delete_task' for individual tasks.

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