render_set_output

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

It discloses non-obvious behaviors: it automatically enables 'save to file', and appends the missing file extension based on the chosen format. Annotations already flag the tool as destructive, and the description adds useful context 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 compact and front-loaded: it states the purpose first, then the key side effects, with no filler. The bilingual format is appropriate for the context and both versions stay concise.

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 full schema coverage and no output schema, the description covers invocation, supported formats, and important side effects. Minor gaps remain around behavior when format is omitted and whether an existing output file would be overwritten, but these do not prevent correct selection or invocation.

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 documents both parameters at 100% coverage, so the baseline is 3. The description adds extra meaning by explaining that a missing extension will be appended from the format and that the output path is absolute, which helps correct parameter usage.

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 states a specific verb and resource: 'Set the render output file path and format', and enumerates the supported formats. This clearly distinguishes it from sibling render_* tools that set resolution, quality, or frame range.

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 gives clear context: this is for configuring the render output path/formats before rendering, and it notes the automatic 'save to file' side effect. It does not explicitly name alternatives or when-not conditions, but the purpose is unambiguous among the render-related siblings.

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