Move task

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

Annotations already declare it as non-read-only, non-destructive, idempotent, and open-world. The description adds one useful behavioral edge case: 'repeating tasks cannot be moved between lists.' However, it does not disclose other potential side effects (e.g., interaction of parent_id and previous_id, or preservation of subtasks when moving lists), so the added value is modest.

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 sentences with no wasted words. The first sentence front-loads the core capabilities, and the second adds a crucial limitation. Every element contributes directly to understanding the tool.

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?

With five parameters, full schema coverage, and no output schema, the description covers the key capabilities and one limitation. It is mostly complete, but could benefit from clarifying how operations combine (e.g., reordering while moving lists) or what happens to subtasks when moving lists. The provided annotations and schema fill many gaps, so the description is adequate.

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 coverage is 100%, so baseline is 3. The description adds meaning by mapping operations to parameters: 'Reorder' cues previous_id, 'make it a subtask' cues parent_id, and 'move it to another list' cues destination_list_id. This helps differentiate the purpose of destination_list_id from the required list_id.

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 multiple specific operations: 'Reorder a task, make it a subtask, or move it to another list.' Each verb references the task resource and unique scopes (position, parent, list), which distinguishes it from sibling tools like update_task or complete_tasks.

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 when to use the tool (when you need to reorder, change parentage, or move lists) but does not explicitly name alternatives or state when not to use it. The only explicit exclusion is the repeating-tasks constraint, which is a limitation rather than a usage guideline.

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