set_render_settings

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

The annotation idempotentHint=true already signals that repeated calls have no additional effect. The description adds little beyond that: it does not mention persistence, side effects, or scope (e.g., active scene). However, since it is a configuration setter, the behavior is largely predictable. The description adds limited context beyond the annotation, so a neutral score is appropriate.

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 extremely concise, with two short sentences. The first sentence states the purpose, and the second lists valid values. No unnecessary words or repetition. The structure is front-loaded with the core action, making it easy to scan.

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?

With 9 parameters and no schema coverage, the description is highly incomplete. It only addresses three parameter values and omits details on critical parameters like resolution, samples, and filepath. The output schema exists but is not referenced in the description, and an agent would need to infer the meaning of many parameters from names alone. This is inadequate for a tool with such breadth.

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 only provides allowed values for three parameters (engine, file_format, color_mode), leaving six parameters (samples, filepath, resolution_x, resolution_y, film_transparent, resolution_percentage) completely unexplained. The description does not clarify units, defaults, or intended use for the remaining parameters, making it insufficient for a 9-parameter tool.

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 clearly states the tool's purpose with a specific verb ('Configure') and resource ('render settings'). It also lists valid values for engine, file format, and color mode, which adds precision. This distinguishes it from sibling tools like get_render_settings (which reads settings) and render_image (which executes rendering).

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 implies usage: you configure settings before rendering, but it does not explicitly state when to use this tool versus alternatives. No mention of when not to use it or reference to get_render_settings for reading. The guidance is implicit but not explicit, so it does not fully aid an agent in choosing between related tools.

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