delete_task

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

No annotations are provided, so the description carries the full burden of disclosing destructive behavior. It merely says 'Delete' without noting that deletion is likely permanent, whether it cascades to related data, or what permissions are required. This is a meaningful gap for a destructive tool.

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 one concise, front-loaded sentence with no filler or redundancy. It names the verb and resource immediately, which is appropriately sized for a simple two-parameter delete operation.

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?

Even though the schema is simple and an output schema exists, the description is incomplete for a destructive operation. It omits irreversibility, side effects, the meaning of zgid, and how group versus personal tasks are selected. An agent would need external knowledge to call this tool with full confidence.

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 0% and the description does not define zgid or task_id beyond the schema titles. The phrase 'group/personal task' hints at a grouping concept but does not explain what zgid should be for a group task versus a personal task, nor how task_id maps to the target task.

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 action ('Delete') and the resource ('task'), and adds a scope qualifier ('group/personal'). This is enough to tell it apart from sibling tools like add_task or update_task_title. It stops short of 5 because it never clarifies what distinguishes a group task from a personal task at the API level.

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 given about when to use this tool versus alternatives. There is no mention of prerequisites like verifying the task exists, nor any suggestion to use get_specific_task first or update_task_title for editing. The only usage signal is the verb itself.

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