clear_completed_tasks

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It importantly reveals that tasks are 'marked as hidden' rather than permanently deleted, which is a non-obvious and critical behavior. It also specifies that user_google_email is required, implying an authentication need. However, it does not mention reversibility or permissions beyond the required email.

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 concise and well-structured. The core purpose is stated in the first sentence, followed by a critical behavioral note. The Args and Returns sections are clearly formatted and contain no unnecessary information.

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 only 2 parameters, both explained in the description. The return type is specified ('str: Confirmation message'). The action and side effect are clear. The description is fully sufficient for an agent to invoke the tool correctly, even without additional schemas or annotations.

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 input schema provides only names and types with no descriptions. The description compensates fully by explaining each parameter: 'The user's Google email address' and 'The ID of the task list to clear completed tasks from.' This completely clarifies the meaning of both required parameters.

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 clearly states the tool's function: 'Clear all completed tasks from a task list.' It uses a specific verb and resource, and the additional note that tasks are 'marked as hidden' distinguishes it from a simple delete. Sibling tools like delete_task and move_task are clearly different in scope.

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 provides clear context for when to use the tool—when you need to clear completed tasks from a list. It does not explicitly mention alternatives or when-not-to-use scenarios, but the context is unambiguous. The required email and list ID give necessary context for invocation.

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