batch_delete_tasks

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

Discloses that the operation is 'MOST DANGEROUS' and that tasks move to trash (recoverable). Without annotations, the description provides key behavioral context, though it could detail concurrency or rate limits.

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?

Extremely concise single sentence with front-loaded deprecation warning. Every phrase adds value (danger, defaults, safety, recovery), no wasted words.

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 dangerous batch operation with no output schema, the description covers purpose, safety, deprecation, and recovery. Lacks details on concurrency or return values, but essential context is present.

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 covers all 4 parameters with descriptions (100% coverage). The description adds critical usage semantics: dry_run defaults to true and confirm is required when dry_run=false, going beyond schema.

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 states 'Batch delete multiple tasks matching a DartQL selector' and notes deprecation with alternative 'execute_dartql', clearly distinguishing from sibling tools like 'delete_task' (single) and 'batch_update_tasks'.

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?

Explicitly mentions deprecation and provides alternative ('use execute_dartql'). Also gives critical safety instructions: dry_run defaults to true and confirm=true required when dry_run=false, guiding correct usage.

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