Record movie / sequence

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

Annotations show write operation (readOnlyHint=false) and non-destructive (destructiveHint=false). Description adds that stop cleans up the recorder node and file is written on the TD machine, providing useful behavioral context beyond annotations.

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?

Two sentences with clear, front-loaded purpose. No unnecessary words. Efficient and well-structured.

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 main workflow, differentiates from siblings, and mentions cleanup. Could mention error handling or file path restrictions, but overall complete for common use.

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%, so baseline is 3. The description adds context about start/stop actions and auto-stop via seconds, but doesn't add significant meaning beyond 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 purpose: 'Record a TOP to a movie file (.mov/.mp4) via a Movie File Out TOP'. It distinguishes from sibling 'render_output' by noting it exports a clip/loop vs single frame.

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 explains when to use (export clip/loop) vs alternative 'render_output' for single frames. It outlines start/stop actions and optional 'seconds' for auto-stop. Not explicit about when not to use, but provides clear context.

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