Export sequence (render)

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

The description discloses that the tool BLOCKS until render finishes and that overwriting an existing output requires confirm:true. It adds valuable behavioral context beyond the annotations (openWorldHint). It could mention return values or error handling, but it is transparent about key behaviors.

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: two sentences, front-loaded with the main action, and no wasted words. Every sentence serves a purpose.

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 has 6 parameters and no output schema, the description covers usage, blocking behavior, overwrite handling, and references a related tool. It is complete enough for an agent to understand when and how to use the tool correctly.

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?

With 100% schema coverage, the baseline is 3. The description adds meaning by noting that outputPath must include an extension matching the preset, presetPath comes from premiere_list_export_presets, sequenceId defaults to active, range defaults to 'entire', and confirm is only needed when file exists. These details enhance schema descriptions.

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 'Render/export a sequence to a media file' using Premiere's built-in direct exporter, and distinguishes itself from sibling tools by specifying the export method. It conveys the action and resource effectively.

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 clear guidance on when to use: provide an output path in an allowed root and a preset path from premiere_list_export_presets. It mentions blocking behavior and overwrite requirement. However, it does not explicitly state when not to use this tool versus alternatives like using Adobe Media Encoder, but given sibling context, this is sufficient.

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