ticktick_move_task

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

With no annotations, the description carries the full burden. It discloses a key behavioral trait: the task is created in the target and completed in the source, not deleted. However, it omits details like permissions, reversibility, or error handling.

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 two sentences long, front-loading the purpose and behavioral detail. Every sentence adds value: first states what it does, second adds behavioral nuance and lists required parameters. No redundant words.

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 tool with no output schema and moderate complexity (3 parameters), the description explains the core behavior and lists required parameters. It covers the essential 'what happens' (create + complete) but lacks examples or edge-case handling. It is sufficient for most use cases but not exhaustive.

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 mentions required parameters but adds only minimal extra meaning beyond the schema descriptions (e.g., 'Required: sourceProjectId, taskId, targetProjectId'). It does not explain parameter values or constraints.

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') and the resource ('from one project/list to another'). It distinguishes itself from sibling tools like ticktick_create_task (creates new) and ticktick_complete_task (completes) by specifying a move operation.

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 lists required parameters but does not provide explicit guidance on when to use this tool versus alternatives. It implies usage by stating the purpose, but lacks 'when not to use' or comparisons with siblings.

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