google_tasks_delete_task

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

With no annotations provided, the description carries the full burden. It correctly flags the operation as permanent and irreversible, but it does not mention permission requirements, rate limits, or what happens if the task is already deleted. However, the description adds value beyond the schema by clarifying the confirmation workflow.

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 sentences covering purpose, usage guidance, and behavioral constraint. Every sentence is necessary and informative with no filler.

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 destructive nature of the tool (no output schema, 3 parameters with low description coverage), the description should ideally mention return values (or lack thereof) and how the tool signals success or failure. The confirmation behavior is well-handled, but the gap on tasklistId and response format limits completeness.

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 only 33% (the confirm parameter has a description, but taskId and tasklistId do not). The description compensates by explaining that confirm must be true and that taskId corresponds to the task shown to the user. However, it does not explain the tasklistId parameter or its default behavior.

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 action ('Permanently delete one task') and specifies the resource ('task'), distinguishing it from siblings like google_tasks_update_task or google_tasks_set_task_completion. The verb 'delete' is precise and unambiguous.

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 explicitly tells the agent to 'first show the exact task to the user' and mandates a confirmation step ('this tool refuses to run without confirm: true'). This provides clear when-to-use guidance and prevents accidental deletion, which is crucial for a destructive operation.

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