delete_tasks

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

With no annotations, the description carries the full burden of behavioral disclosure. It explains the input format but does not state whether deletion is permanent, how missing tasks are handled, or whether batch deletion is atomic. This is a significant gap for a destructive mutation 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 well-structured: a one-line purpose, clear mode explanation, explicit args with required fields, and illustrative examples. Every sentence adds value, and there is no unnecessary verbosity.

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 is simple, and the description thoroughly covers input requirements for both single and batch deletion. While it lacks details on return values or error behavior, the presence of an output schema likely covers that. Overall, it is sufficient for correct invocation.

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 schema is very generic (anyOf object/array with additionalProperties), providing no field-level detail. The description compensates by explicitly requiring project_id and task_id, clarifying single vs list inputs, and providing concrete examples. This makes parameter usage unambiguous.

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 opens with 'Delete one or more tasks,' clearly identifying the verb and resource. It also distinguishes itself from sibling tools like update_tasks or complete_tasks by explicitly focusing on deletion and supporting batch operations.

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 usage is implied: if you want to delete tasks, use this tool. However, there is no explicit guidance on when to prefer this over alternative tools (e.g., for completing tasks) or any exclusions. The description does not mention alternatives like delete_projects or complete_tasks.

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