batch_complete_task

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

Discloses parallel execution, concurrency cap (5), per-item failure handling for already completed/deleted tasks, and return format. Annotations only state it's not read-only and not destructive; description adds significant behavioral context.

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?

Concise, front-loaded with action, then usage, then technical details, then return format. Every sentence adds value, no redundancy.

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 single-parameter tool with no output schema, description fully covers usage, behavior, return format, and error handling. No gaps.

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 fully covers 'ids' parameter. Description adds context about parallel execution, caps, and error handling, but does not change parameter meaning. High schema coverage gives baseline 3; added value justifies 4.

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?

Description clearly states the action ('Mark...COMPLETED'), resource ('tasks'), and scale ('1–50 tasks'). It distinguishes from sibling 'complete_task' by specifying batch parallelism.

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?

Provides explicit usage scenarios ('end-of-week catchups', 'close all...') and implies when to use the singular alternative (complete_task). No explicit when-not, but context makes it clear.

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