ticktick_batch_delete_tasks

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

Annotations provide destructiveHint=true and idempotentHint=true, indicating this is a non-reversible operation that can be safely retried. The description adds valuable context with the warning 'This action cannot be undone,' reinforcing the destructive nature and providing user-facing caution beyond the 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 extremely concise with two sentences: one stating the purpose and another providing a critical warning. It is front-loaded with the main action and wastes no words, making it easy to parse quickly.

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 (destructive batch operation), annotations cover safety (destructive, idempotent), and an output schema exists, reducing the need for return value details. However, the description lacks parameter guidance and usage context, making it minimally adequate but with clear gaps for effective agent use.

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 description coverage is 0%, with no descriptions for the 'tasks' array or its items. The description does not compensate by explaining what 'tasks' should contain (e.g., task IDs, project IDs) or the format, leaving parameters largely undocumented beyond the schema's structure.

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 ('Delete multiple tasks') and scope ('in a single request'), which is specific and distinguishes it from the sibling 'ticktick_delete_task' that likely handles single deletions. However, it doesn't explicitly mention the resource type (tasks) beyond the name, though this is implied.

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 guidance on when to use this tool versus alternatives like 'ticktick_delete_task' for single deletions or other deletion tools. It lacks context about prerequisites, such as needing task IDs, or when batch deletion is preferred over individual calls.

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