remove_motion_blur

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

With no annotations, the description must carry the burden. It states the tool creates new clips, returns names of items, and lists deblur_option keys. It does not disclose whether operations are destructive, idempotent, or error conditions. More detail on behavior beyond creation would improve transparency.

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 concise and well-structured. It starts with a clear purpose sentence, then explains usage and parameters efficiently. The deblur_option keys are presented in a bullet-like format in the text, making it easy to parse. No unnecessary words.

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's complexity (3 parameters, one nested object), and the existence of an output schema (though not shown), the description explains input thoroughly and mentions the return (names of new items). It could be more complete by describing the output structure, but it covers the essential behavior.

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 description provides an 'Args' section that explains each parameter (clip_name, folder_path, deblur_option) and details the nested keys for deblur_option (e.g., 'FileName', 'Format', 'Codec'). Since the input schema has no descriptions, the description fully compensates and adds significant meaning.

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's purpose: 'Apply AI motion deblur to a clip or folder, creating new deblurred clips.' The verb 'apply' and resource 'motion deblur' are specific, and it distinguishes from sibling tools like apply_cdl_from_file by focusing on deblurring.

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 explains when to use the tool: it operates on a single clip, a folder, or the current folder. It also mentions a prerequisite ('Requires Resolve Studio with motion deblur support'). However, it does not provide guidance on when not to use it or mention alternative tools for similar tasks.

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