tasks_tasks_move

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

The description aligns with annotations (readOnlyHint=false) by indicating a write operation. It discloses the core behavior: moving within or between lists via positioning parameters. However, it does not detail potential side effects (e.g., removal from old list, permission requirements) or confirm non-destructiveness beyond the implied move.

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 extremely concise (two sentences, 20 words) and front-loaded with the action. Every sentence provides essential information without 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?

Given the 5 parameters, 2 required, and no output schema, the description adequately covers the operation by explaining the key parameters and their purposes. It omits potential edge-case behaviors (e.g., moving from a subtask position), but remains complete for typical use.

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 description adds value beyond the schema by clarifying the roles of 'parent' and 'previous' for ordering, and 'destinationTasklist' for changing lists. Since schema coverage is 100%, the baseline is 3; the extra usage context justifies a 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?

The description clearly states the action 'Move a task within its list or to another list', specifying the resource (task) and scope (within or between lists). It distinguishes from sibling tools like tasks_tasks_update or tasks_tasks_list by focusing solely on relocation and reordering.

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 explicit guidance on parameter usage: 'Use parent/previous to set position; destinationTasklist to change list.' It implies when to use each parameter, though it does not explicitly exclude alternatives or state when not to use the tool. For a move operation, this is sufficient.

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