delete_bulk_tasks

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

No annotations are provided, and the description only states the obvious destructive action without disclosing important traits such as irreversibility, partial failure behavior, or permission requirements. The schema hints at a max of 100 tasks, but the description adds no behavioral context.

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 a single, concise sentence with no wasted words. However, it is slightly too brief for a tool with three parameters, missing an opportunity to add value without significantly increasing length.

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 (3 parameters, no output schema, no annotations), the description is insufficient. It fails to explain return values, error handling, the purpose of 'custom_task_ids', or how the tool behaves in edge cases.

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 input schema covers 67% of parameters with descriptions (task_ids and team_id). The tool description does not add any additional meaning beyond the schema. With baseline 3 for mid-range schema coverage, no extra value is provided.

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 'Delete many tasks at once' uses a specific verb and resource, clearly indicating a bulk delete operation. It effectively distinguishes itself from the sibling tool 'delete_task' by emphasizing the capability to delete multiple tasks simultaneously.

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 provides no explicit guidance on when to use this tool versus alternatives like 'delete_task'. It does not mention any prerequisites, limitations (e.g., max 100 tasks, already in schema), or scenarios where single deletion is preferable.

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