clear_completed_tasks

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

Annotations already flag destructiveHint=true and idempotentHint=true, but the description adds the crucial nuance that the operation only hides tasks and is reversible via list_tasks with include_completed=true. It also discloses the user-confirmation requirement, which is behavioral context not present in the annotations.

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 short sentences with zero waste. The core action is front-loaded, followed immediately by the non-destructive clarification and retrieval path.

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 has an output schema, so return values need not be explained. The description covers reversibility, the user-confirmation prerequisite, and how to retrieve hidden tasks afterward, which is complete for a two-parameter, idempotent hide operation.

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 50%. The task_list_id parameter is well documented in the schema, but the confirm boolean has no schema description. The description alludes to confirmation ('after user confirmation') without explaining that it maps to the confirm flag or that it defaults to false, so it only partially compensates for the schema gap.

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?

States a specific verb and resource: 'Hide completed tasks.' The follow-up sentence distinguishes the operation from permanent deletion, which is exactly the confusion an agent could have among siblings like delete_task and delete_task_list.

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 gives a clear prerequisite ('after user confirmation') and a retrieval alternative ('list_tasks with include_completed=true'). It does not explicitly say when not to use this tool versus deleting individual tasks or deleting a whole list, but the context is strong enough to route correctly.

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