Render output to file

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

Description adds that the file is written on the TD machine, which is beyond annotations (readOnlyHint=false, destructiveHint=false). However, it does not disclose overwrite behavior or what happens if file exists, which could be expected for a write operation.

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 zero waste. Front-loaded with purpose, then alternate tool contrast, then path instruction. Every sentence adds value.

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 write tool with rich annotations and schema, the description covers purpose, target machine, path format, and usage context. No output schema needed, as it's a file-writing operation.

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 description adds minimal new info beyond schema descriptions (e.g., mentions supported formats). Baseline 3 is appropriate as schema already explains parameters well.

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?

Description clearly states the tool saves a TOP to an image file at native resolution, with explicit verb 'Save' and resource 'TOP to image file'. It distinguishes from sibling 'get_preview' by contrasting export of finished frame vs inline thumbnail.

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?

Provides context for usage: 'for exporting a finished frame' and explicitly contrasts with 'get_preview' for inline thumbnails. Also instructs to pass an absolute path. Lacks explicit when-not to use but clear enough.

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