Move List into Folder

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

There are no annotations, so the description carries the full burden, but it does not add behavioral context beyond the schema. The special sentinel values for removal are already described in the input schema, and the description merely repeats them. It lacks disclosure of side effects, error behavior, or any other non-obvious traits.

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 three sentences and efficiently front-loads the core action, then explains the two usage modes, and ends with the sibling reference. No redundant or verbose phrasing; every sentence contributes.

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 simple 2-parameter tool with no output schema, the description covers the essential purpose, usage modes, and how to find prerequisite IDs. It is complete enough for an agent to select and invoke the tool correctly, though it omits return value details which may be assumed.

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% for both parameters, so the baseline is 3. The description does reiterate the folder_id semantics ('Pass a folder_id... pass an empty string...') but this is exactly what the schema already states, adding no new meaning. It does not elaborate on project_id beyond its schema description.

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 tool moves a project/list into a folder or removes it from a folder, using specific verbs and resources. It distinguishes itself from task-moving tools by explicitly mentioning 'project folder' and the removal variant. This is unambiguous and differentiates from siblings like ticktick_move_task.

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 when to use the tool (to move a project into or out of a folder) and how to use it (pass folder_id or sentinel values). It directly references a sibling tool (ticktick_get_project_folders) for finding folder IDs, which is a clear alternative and prerequisite. This is strong usage direction.

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