remove_videos_from_folder

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

Annotations already indicate the operation is neither read-only nor destructive by default, but the description adds crucial behavioral nuance: the default is non-destructive unfiling, while delete_videos_too causes permanent destruction and requires confirm. This goes beyond the structured annotations and meaningfully informs the agent of irreversible consequences.

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 tight sentences with no filler. The primary action and default behavior are front-loaded, and the permanent-deletion caveat is placed exactly where it matters.

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 schema and annotations, the description covers the essential behavioral context: what the call does, the default non-destructive path, and the destructive exception. It is complete enough for correct invocation, though it does not describe the response format since no output schema exists.

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 description coverage is 100%, so the schema already documents folder_id, video_ids, confirm, and delete_videos_too. The description adds the relationship between confirm and delete_videos_too, but that is also present in the schema. It provides no additional parameter-level meaning beyond the structured schema.

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 specific verb and resource: removing videos from a folder in one call. It also clarifies what this means functionally (unfiling, not deletion), which distinguishes it from delete_video and other removal-like siblings.

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 clearly explains the default behavior (unfile and return to main library) and the destructive alternative (delete_videos_too). It does not explicitly name sibling alternatives like delete_video, but the contrast between unfiling and permanent deletion gives enough context for an agent to choose appropriately.

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