clear_completed_tasks

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

Discloses that tasks are 'marked as hidden' rather than deleted, but lacks details on authentication needs, rate limits, or reversibility. With no annotations, the description carries full burden but only partially fulfills it.

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?

Main description is two sentences followed by structured Args/Returns. Front-loaded with purpose, but the docstring format adds a few extra lines without being verbose.

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?

Covers purpose, parameters, and basic behavior (hidden). With output schema present, return values are already documented. Lacks context on permissions, side effects, or restoration of hidden tasks, making it slightly incomplete.

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 description coverage is 0%, but the description explicitly lists each parameter with its purpose, default for dry_run, and required status, adding significant meaning beyond the raw schema.

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?

Clearly states 'Clear all completed tasks from a task list' with specific verb and resource. Distinguishes from siblings like delete_task or update_task by focusing on completed tasks as a group.

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?

Describes the action but does not explicitly state when to use vs alternatives (e.g., delete_task for individual tasks). The dry_run parameter implies testing, but no direct 'use this when' guidance.

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