Update tasks in bulk

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

Annotations already declare destructive/read-only traits. The description adds useful behavioral context: it supports preview mode (dry-run), bounded concurrency, and per-item results. However, it does not describe confirmation flow or failure behavior.

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?

A single concise sentence that front-loads the action and packs in three behavioral modifiers (preview, bounded concurrency, per-item results) with 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?

This is a complex bulk tool with no output schema, yet the description omits important context: confirmation flow, default parameter values, return format, and error handling. The one-liner is too sparse for effective 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%, so the description must compensate, but it only hints at 'preview' for the dry_run parameter. The confirm, confirmation_token, and items parameters are not explained beyond their schema names.

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 identifies the action ('preview or update'), the resource ('multiple tasks'), and differentiates from siblings like update_task (single task) and create_bulk_tasks (creation). It is specific and not a tautology.

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 phrase 'multiple tasks' implies batch usage, and 'preview' suggests a dry-run capability, but it does not explicitly state when to use this tool over alternatives or mention exclusions. No sibling tools are named as alternatives.

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