tasks_tasks_delete

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

The description discloses an important side effect beyond the annotations: if the task was assigned from Docs/Chat Spaces, the original is also removed. Combined with the destructiveHint annotation, the agent understands the mutation is real and has potential cross-resource impact. It does not mention idempotency behavior, but idempotentHint already covers that.

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 short sentences with no filler. The core action is front-loaded, and the caveat about Docs/Chat Spaces is placed immediately after, making the description easy to scan and parse.

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?

For a simple destructive operation with no output schema, the description provides the essential action and critical side effect. It lacks explicit guidance about permanent deletion or how it relates to tasks_tasks_clear, but annotations and the sibling list partially compensate.

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 100%, so both parameters (task and tasklist) are already clearly documented in the schema. The description adds no additional parameter-level meaning, such as how the tasklist scopes the deletion or whether task IDs are globally unique.

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 states a specific verb ('Delete') and resource ('a task'), immediately distinguishing it from list, update, and move operations. The additional clause about Docs/Chat Spaces origin behavior further specifies the exact scope of deletion.

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 makes the basic usage context clear: use this when you want to delete a single task. However, it does not explicitly contrast with the sibling 'tasks_tasks_clear' or mention cases where alternative deletion approaches might be preferred, leaving some routing judgment to the agent.

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