batch_update_tasks

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

No annotations are provided, so the description carries the full burden. It warns about destructive behavior (batch update) and emphasizes dry_run. It mentions full replacement semantics for relationships but lacks details on rate limits, partial failures, or auth requirements.

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 very concise with three sentences. It front-loads the deprecation and alternative, then states the function, and ends with a critical warning. Every sentence earns its place.

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?

The tool is complex (batch update with relationships, multiple parameters) and has no output schema. The description does not mention return values (e.g., count of updated tasks, errors). It covers the deprecation and safety but lacks completeness about behavior post-execution.

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 100% and the schema itself provides detailed parameter descriptions. The description adds value by summarizing that it 'Supports all task fields including relationships' and reiterates the dry_run criticality, but does not add new meaning beyond the 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 clearly states the tool is deprecated and recommends execute_dartql as an alternative. It specifies 'Batch update multiple tasks matching a DartQL selector', which is a specific verb and resource, and distinguishes from siblings like execute_dartql.

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 an explicit alternative (execute_dartql) and a critical safety guideline ('Always use dry_run=true first to preview changes!'). However, it does not elaborate on when not to use this tool beyond deprecation.

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