ffkit_merge

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

Without annotations, the description fully carries the burden of behavioral disclosure. It states that the tool concatenates media files, explains two merge strategies (fast vs re-encodes), and implies the output is a single file. This is clear and sufficient for a straightforward tool with no destructive or auth concerns. No contradictions exist.

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?

Two sentences, zero wasted words. Each sentence earns its place: the first states the purpose, the second gives usage guidance. The structure is front-loaded with the action first, followed by method-specific 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 no output schema and simple parameters, the description adequately covers what the tool does and how to choose the method. It could be slightly more complete by mentioning the file format requirement for concat_demuxer (same codec), but the 'same codec' hint suffices. No critical gaps remain.

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%, so the schema already describes each parameter. The description adds value by explaining the trade-off between concat_demuxer (fast, same codec) and concat_filter (re-encodes, cross-format) – critical semantic context beyond the schema's enum labels. Input_paths and output_path are self-explanatory, so no extra detail needed.

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 uses a specific verb ('Concatenate') and resource ('multiple media files') that clearly states the tool's function. It also distinguishes between two methods (concat_demuxer vs concat_filter), adding precision. Among sibling tools like ffkit_clip or ffkit_extract_audio, this description uniquely identifies merging behavior.

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 explicit guidance on when to use each method (same codec vs cross-format), which helps the agent choose correctly. However, it does not mention when not to use this tool versus alternatives like ffkit_clip or ffkit_transcode for related tasks (e.g., trimming or conversion).

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