Bulk Delete Project Tasks

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

Annotations already mark destructiveHint: true. The description adds that deletion is permanent and cannot be undone, along with the required parameters and API endpoint details, enhancing transparency beyond annotations.

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 somewhat repetitive ('cannot be undone' stated twice, 'permanently removes' duplicated). It could be more concise without losing clarity. The endpoint info is useful but adds 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?

For a destructive operation with no output schema, the description covers input requirements and permanence. However, it does not mention what happens upon success (e.g., empty response or confirmation), leaving some gap.

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?

Input schema already has 100% coverage with descriptions for both parameters. The description repeats the required parameters but adds no new meaning beyond what the schema provides, hence baseline 3.

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 tool deletes Bid Board records permanently and specifies it uses an array of task IDs. The verb (permanently delete) and resource (Bid Board records) are explicit. However, the title says 'Project Tasks' while description says 'Bid Board records', causing slight ambiguity.

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 indicates when to use (to permanently delete Bid Board records) and notes the action cannot be undone. But it does not differentiate from sibling tools like singular delete or other bulk delete versions, providing no guidance on alternatives.

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