Record movie / sequence

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

The description adds behavioral context beyond the annotations: it explains the start/stop workflow, that stop cleans up the recorder node, and that the file is written by TouchDesigner on the TD machine. With annotations already indicating a non-read-only, non-destructive operation, the description provides useful extra detail without contradicting them.

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 three sentences long, front-loaded with the main purpose, and every sentence delivers critical information. No redundancy or 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 tool with 5 parameters and no output schema, the description covers the workflow (start/stop/auto-stop), the file location, the TD machine context, and the alternative for single frames. It is sufficiently complete for an agent to select and invoke 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?

Schema coverage is 100%, and the description enriches the parameter semantics by explaining how start uses file and fps, seconds auto-stops after a fixed length, and stop finishes recording and cleans up. This is a clear added value over the raw 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 the tool records a TOP to a movie file via a Movie File Out TOP, with a specific verb and resource. It explicitly distinguishes itself from render_output, which only saves a single frame, making its purpose unambiguous.

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 explicitly says to use this tool for exporting a clip or a loop, while recommending render_output per frame for individual numbered frames. This gives clear when-to-use and when-not-to-use guidance, directly naming the alternative.

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