move_bulk_tasks

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

With no annotations, the description carries full burden for behavioral disclosure. It mentions 'adds them to the list' and 'multi-list association', but the term 'move' is ambiguous—it does not clarify whether tasks are removed from other lists or if this is a purely additive operation. No information on idempotency, permissions, rate limits, or side effects.

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 a single sentence that conveys the core purpose and a key detail about multi-list association. It is concise and front-loaded, but could benefit from a slight restructuring to include behavioral notes.

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 mutation nature (no annotations, no output schema) and the presence of similar sibling tools ('add_task_to_list', 'update_bulk_tasks'), the description lacks information about return values, error handling, and whether the operation is reversible or has dependencies. The agent needs more context to use this tool correctly.

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?

Both parameters have clear descriptions in the schema (task_ids: 'max 100 per call', list_id: 'Destination List ID'), achieving 100% schema coverage. The tool description adds no additional meaning beyond what the schema already provides, so baseline score of 3 is appropriate.

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 ('Move many tasks'), the resource ('tasks'), and the target ('into a target List'). The parenthetical 'adds them to the list; uses multi-list association' adds specificity and helps distinguish from single-task operations like 'add_task_to_list'.

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 implies bulk usage via 'many tasks' and 'multi-list association', but does not explicitly state when to use this tool vs alternatives like 'add_task_to_list' or 'update_bulk_tasks'. No exclusion criteria or prerequisites are provided.

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