export_render

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the external melt dependency and the pipeline from project to MLT XML to melt. However, it does not disclose whether rendering blocks, whether existing files are overwritten, or what side effects/return behavior occur after invocation.

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 compact and front-loaded: a one-sentence summary, a two-sentence implementation note, a prerequisite, and a tight Args block. Every sentence adds value, and there is no redundant or filler content.

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 two-parameter tool with an output schema, the essential call shape is covered. Still, the description is incomplete in context: it does not explain how export_render relates to render_queue_* or whether this is a synchronous blocking operation, and it omits overwrite/side-effect behavior. An agent would need to infer these aspects from sibling names.

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 input schema has 0% description coverage, but the Args section adds meaningful semantics: output_path is defined as the destination video file with an example, and preset is described as optional with a pointer to export_list_presets. This compensates well for the sparse schema, though it could be richer about accepted file extensions or preset value formats.

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 opens with a specific verb and resource: 'Render the project to a video file via melt.' It further clarifies the mechanism by stating it generates MLT XML and pipes it through melt, which clearly separates it from siblings like export_xml (XML output) and render_queue_* (queued rendering).

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 implies its use for direct video rendering and provides a prerequisite ('Requires melt on the system') plus a cross-reference to export_list_presets for presets. However, it does not explicitly state when to use this tool instead of render_queue_add/start or export_xml, nor does it mention excluded scenarios.

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