set_render_settings

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

With no annotations, the description must fully disclose behavior, but it only mentions engine_settings passthrough to scene.eevee / scene.cycles. It does not state that this tool mutates the scene, that all parameters are optional and only set non-null values, or any side effects or prerequisites. The behavioral disclosure is minimal.

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 a single concise line that front-loads the engine options and passthrough behavior. It is efficient with no filler, though the brevity sacrifices essential detail. Structure is clear but minimal.

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 12 optional parameters, no output schema, and no annotations, the description is drastically incomplete. It does not explain the effect of each parameter, typical usage, return values, or side effects. An agent cannot reliably call this tool without additional documentation.

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 0%, so the description must compensate. It explains the engine values and engine_settings passthrough, but ignores fps, denoise, samples, color_mode, percentage, resolution, file_format, motion_blur, output_path, and film_transparent. These parameters remain unexplained, leaving the agent without meaning for most inputs.

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 it sets render settings and specifies the engine choices and engine_settings passthrough, but it does not mention the other ten parameters (fps, resolution, samples, etc.), nor does it differentiate itself from sibling tools like get_render_settings or set_color_management. It conveys the core purpose but lacks scope completeness.

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?

There is no guidance on when to use this tool versus alternatives such as get_render_settings, list_render_engines, or set_color_management. No conditions, exclusions, or recommended usage scenarios are provided, leaving the agent to infer when this is appropriate.

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