pipeline

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

With no annotations, the description still discloses important behavior: one re-encode, no intermediate files, reusable saved steps, and dryRun returning the plan without execution. It does not cover permissions, error handling, or normal return values in detail, but it adds substantial behavioral context beyond the schema.

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 four sentences, front-loaded with the core purpose and performance benefit. Every sentence contributes useful information about supported steps, reuse, and dryRun, with no filler.

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 complex nested pipeline tool, the description covers the central concept, supported operations, export endings, reuse, and dryRun. It leaves normal return values and the exact save/re-run mechanism implicit, but the detailed schema fills most structural gaps.

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 parameter meaning is already largely documented in the schema. The description adds useful context by saying steps use the same options as the standalone tools and may end with export_preset or export_gif, but most parameter-level semantics remain in the 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 gives a specific verb and resource: run several edits as one ffmpeg process. It distinguishes itself from the standalone edit tools by explaining that it avoids a tool call and re-encode per edit. The listed supported operations and final export steps make its scope clear.

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?

It clearly implies when to use this tool: for multiple edits that should share one re-encode instead of separate standalone tool calls. It also names the standalone tools as the alternative behavior, though it does not explicitly say when a single edit should use those tools instead.

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