Build video from edit-spec

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

Description adds behavioral info beyond sparse annotations: it returns a per-step report with warnings, and applies even if some steps fail. Does not mention auth or rate limits, but openWorldHint covers some context.

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?

Three sentences, front-loaded with purpose, then components, then additional notes. Efficient but could be more structured with bullet points for clarity.

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?

Covers assembly steps, asset path requirement, optional rendering, and return value. No output schema, but return value described adequately. Could be more explicit about working on active sequence.

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 baseline 3. Description does not add significant meaning beyond schema parameter descriptions; it echoes them without deeper guidance.

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?

Clear verb 'Assemble a whole timeline' and lists specific actions (create sequence, place clips, add titles, audio, transitions, effects, render). Distinguishes from siblings like premiere_add_audio, etc., as the bulk assembly tool.

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?

States it is the 'main fully-automatic assembly tool' and notes asset paths must exist. Lacks explicit when-not-to-use or alternatives, but context from siblings implies use for full builds.

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