media_pool_move_clips

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

No annotations are present, so the description carries full burden for behavioral disclosure. It indicates a mutation (move) but does not disclose side effects, reversibility, prerequisites, or error behavior. The schema adds some info about target folder search scope, but the description itself is sparse.

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?

A single, focused sentence that communicates the essential action with zero redundancy. Front-loaded and efficient.

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?

The tool is simple, and the schema covers parameters; output schema exists. However, with no annotations and minimal description, behavioral context (like what happens on failure or whether clips are removed from the source) is incomplete. Adequate but not comprehensive.

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%, and parameter descriptions are informative (e.g., target folder searched in current folder's siblings and root children). The description does not add meaning beyond the schema, but the baseline of 3 applies due to full schema coverage.

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 'Move clips from the current folder to a different Media Pool folder,' using a specific verb and resource. It distinguishes itself from siblings like media_pool_delete_clips or media_pool_relink_clips by defining the action of relocating clips between folders.

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 implies usage for reorganizing clips in the Media Pool but does not explicitly state when to use it vs alternatives. No exclusions or alternative tool references are provided. The context is clear but not elaborated.

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