Clear completed tasks

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

Annotations already mark destructiveHint=true, but the description adds crucial nuance: it hides rather than deletes, tasks remain retrievable with status=completed, and the action is not reversible via the API. This goes beyond the simple destructive flag.

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?

Two concise sentences: first states purpose and UI analogy, second explains the hidden-but-retrievable outcome and irreversibility. Front-loaded and zero fluff.

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 single-parameter tool with no output schema and clear annotations, the description covers all essential aspects: what it does, how it behaves, how to recover, and reversibility. Sibling tools are implicitly differentiated via the 'hide not delete' nuance.

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 'list' is fully described in the schema (id or title, default list, lookup via list_tasklists). The tool description adds no extra parameter semantics, so baseline score of 3 is appropriate given 100% schema coverage.

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?

Description clearly states the action (Hide all completed tasks) and the resource (in a list), with a useful UI analogy. It distinguishes itself from sibling tools like delete_task by noting tasks remain retrievable.

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?

Provides clear context: it mimics the 'Clear completed' UI action, and notes tasks stay retrievable via list_tasks status=completed, implying when to use instead of delete. Warns it is not reversible via API, but does not explicitly name alternative tools for permanent deletion.

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