move_clips_to_folder

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

With no annotations, the description must disclose behavioral traits. It states the operation is a move but does not clarify if clips are deleted from source, whether it overwrites duplicates, or if permissions are required. The behavior around non-existent folders or clips is not described.

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 and a parameter list—with no redundant information. It is front-loaded with the core action and efficiently conveys the necessary parameter details.

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 tool has a move operation, two parameters, no annotations, and an output schema that is not described, the description is incomplete. It fails to explain return values, error conditions, or side effects like whether clips are removed from the source folder. The parameter descriptions are too brief to fully cover potential usage.

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 0% so the description must add meaning. It provides a brief explanation for each parameter: clip_names as 'List of clip names to move' and target_path as 'Destination folder path' with an example. This adds marginal value over the schema structure but does not specify constraints like valid characters or path format.

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 name and description clearly state the action (move) and resource (clips to a folder). The description explicitly says 'Move clips from the current folder to a target folder', which is a specific verb+resource and distinguishes it from sibling tools like delete_clips or rename_clips.

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 no guidance on when to use this tool versus alternatives such as set_current_folder or rename_clips. It does not mention prerequisites like folder existence or that clip names must be valid. No explicit context about when not to use it.

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