render_set_format_and_codec

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

No annotations are provided, so the description must disclose behavioral details. 'Set the render format and codec' only conveys a mutation; it does not state whether the change persists, affects current render jobs, requires a preset, or what errors occur for invalid combinations.

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?

A single short sentence that is front-loaded and free of filler. It is concise, though it borders on under-specification; the schema carries the parameter detail.

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?

Despite complete parameter schema, the tool description lacks usage context and behavioral disclosure. For a state-changing operation with no annotations, more information (e.g., relationship to render presets, invalid input handling) is needed for an agent to invoke it safely.

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 description coverage is 100%, with both format_name and codec_name documented including an example and cross-reference to valid-combination getters. The description adds no additional parameter meaning, so the baseline of 3 applies.

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 'Set' and names a precise resource ('render format and codec'), clearly identifying the tool's function. It distinguishes itself from sibling getters like render_get_format_and_codec and the broader render_set_settings.

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 provides no guidance on when to use this tool versus alternatives such as render_set_settings or how to discover valid format/codec combinations. The schema's codec_name description mentions render_get_formats() and render_get_codecs(), but that guidance lives in the parameter schema, not in the tool description.

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