Render output to file

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

Annotations indicate a write operation with side effects, and the description adds key context: the file is written by TouchDesigner on the TD machine and an absolute path is required. This helps prevent path confusion. It does not disclose overwrite behavior, but the annotations already signal side effects.

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 pack all essential information: action, formats, contrast with sibling, and file location. No wasted words; front-loaded with the core 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?

For a simple 2-parameter file-export tool, the description covers purpose, formats, resolution, and machine location. It lacks explicit overwrite semantics, but the schema and annotations fill most gaps, making it sufficiently complete.

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 already provides 100% coverage, including the fact that the file path is on the TD machine and extension picks format. The tool description repeats this information but does not add new meaning beyond the schema.

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 uses a specific verb 'Save a TOP to an image file' with resolution detail, and explicitly contrasts with get_preview to clarify its unique role. It clearly identifies the resource (TOP) and the action (exporting full-res image).

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 states 'unlike get_preview which only transfers a small inline thumbnail', providing an explicit named alternative and context for when to use this tool (exporting a finished frame). It could more explicitly say 'use for full-res export, not for quick previews', but the contrast is clear.

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