delete_task_list

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

With no annotations, the description carries the full burden. It discloses the key destructive behavior (deleting all tasks in the list) and the dry_run behavior. However, it does not mention authentication requirements or reversibility.

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 with a clear structure: main effect, bulleted args, and return. The return description ('str: Confirmation message') is vague but brief. Overall efficient, though word count is acceptable.

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?

Given the tool's complexity (destructive, 3 params, no annotations), the description covers the essential effect and dry_run behavior. The output schema exists, so detailed return explanation is unnecessary. It is reasonably complete.

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%, so the description must compensate. It explains the dry_run parameter's role but provides minimal detail for user_google_email and task_list_id beyond what the schema already indicates. The added value is average.

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 'Delete a task list' and notes the cascading deletion of all tasks in the list. This specific verb+resource distinguishes it from sibling tools like delete_task and clear_completed_tasks.

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?

No guidance is provided on when to use this tool versus alternatives like delete_task or clear_completed_tasks. The dry_run parameter is mentioned but not elaborated on for usage context.

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