delete_bulk_tasks

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

Discloses that the operation is permanent and cannot be undone, and mentions the per-task success/error report. Since no annotations exist, the description carries the full behavioral burden and does so adequately.

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 with no wasted words. Front-loaded with the core purpose and key constraint (100 max), followed by the important return information. Highly efficient.

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 description covers the main aspects: action, constraints, permanence, and return value. No output schema exists, so the report mention is helpful. Could optionally mention prerequisites like permissions, but overall sufficient for a bulk deletion tool with good schema coverage.

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 100%, so the description adds little beyond what's already in the schema. It confirms the 100-task limit but does not enrich parameter meaning further. Baseline score of 3 is appropriate.

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 ('Permanently delete many tasks at once'), the resource ('tasks'), the scope ('up to 100'), and distinguishes from single-task deletion via sibling 'delete_task' tool. It is specific 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 implies usage for bulk deletion but does not explicitly state when to use this tool over sibling 'delete_task' or other alternatives. No exclusions or conditions provided, leaving the agent to infer context.

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