add_videos_to_folder

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

The description adds valuable behavioral context beyond the annotations: a video lives in one folder at a time, so the operation moves rather than copies. This clarifies a non-obvious consequence of the call. The annotations already cover idempotency and non-destructiveness, so no contradiction exists.

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?

Three concise sentences that front-load the core action, then add efficiency guidance and the critical move-not-copy caveat. Every sentence earns its place with no 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?

For a simple two-parameter tool, the description covers the key behavior an agent needs to know: batch operation, move semantics, and efficient usage. There is no output schema, but the absence of return-value details is acceptable given the operation's simplicity.

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 schema already provides 100% coverage for both parameters, including the destination folder id and the list of video ids with a max of 100. The description reinforces the batch usage but does not add substantial new meaning beyond what the schema states.

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 states a clear, specific action: 'Add one or many videos to a folder in a single call.' It also distinguishes itself by explaining the move-not-copy behavior, which differentiates it from related tools like remove_videos_from_folder.

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 gives explicit usage context, recommending it for filing a back catalog efficiently and advising to pass the whole list rather than calling once per video. It does not explicitly name sibling tools to avoid, but the guidance is clear enough for correct selection.

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