Bulk Delete Project Tasks

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

The description reinforces the destructive nature from annotations ('cannot be undone', 'permanently removes'), adding behavioral context beyond the annotations alone.

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 relatively short but includes repetition ('This cannot be undone' twice). It front-loads the action and usage, though it could be slightly more compact.

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 delete operation without output schema, the description covers purpose, usage, and permanence. It lacks response details or error handling, but it is adequate given the tool's simplicity.

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 description adds critical information about the request body (array of task IDs) that is absent from the input schema, which only defines path parameters. This is essential for correct usage.

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'), the resource ('Estimating records'/tasks), and emphasizes irreversibility. It distinguishes from siblings by specifying 'Estimating' records, which is unique among bulk delete tools.

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 explains how to use it (array of task IDs in request body) and lists required parameters. It lacks explicit when-not-to-use or alternative tools, but the context is clear.

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