move_task_between_lists

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

With no annotations provided, the description carries the full burden. It discloses the destructive step ('delete it from the source list') and explains why the operation is structured this way. However, it does not warn that recreation likely produces a new task ID or may lose metadata, which is an important behavioral consequence for an agent to know.

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?

Two compact sentences with no wasted words. The core behavior is front-loaded, and the parenthetical rationale adds important context without bloating the description.

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 description explains the underlying recreate+delete mechanism and the general purpose, which is helpful. However, it omits critical operational details such as non-atomicity, possible duplicate tasks if deletion fails, and whether the recreated task keeps all original properties. With no output schema, these gaps are not filled elsewhere.

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?

The schema already documents 'provider' and 'toListId', but leaves 'taskId' and 'fromListId' undocumented. The description adds meaning by mapping 'existing task' to taskId, 'another list' to toListId, and 'source list' to fromListId, compensating for the schema gaps.

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 states a specific verb+resource combination: it recreates an existing task in another list and deletes it from the source list. It also explains the reason (Graph To Do has no native move), which clearly distinguishes this tool from create_task and delete_task siblings.

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 gives a general use case ('Use to reorganize') and implies it should be used when moving tasks between lists, but it does not explicitly state when not to use it or name alternatives. The lack of explicit routing to/from sibling tools leaves some ambiguity.

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