set_render_settings

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

Annotations only provide idempotentHint. The description does not disclose side effects (e.g., whether it resets other settings), what happens with invalid values, or that it modifies the current scene. It adds no behavioral context beyond the annotation.

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 very concise, just two lines, with the main action front-loaded. The lists compactly provide useful parameter values without unnecessary text.

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 0% schema coverage, the description is too sparse. It only covers three parameters and provides no context on when to use the tool or what the tool actually does beyond 'configure'. The presence of an output schema doesn't compensate for missing parameter guidance.

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 0%, so the description's enumeration of valid values for engine, file_format, and color_mode is helpful for those three parameters. However, it does not cover the other six parameters (samples, resolution, filepath, film_transparent, resolution_percentage), leaving them undocumented.

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 has a clear verb+resource ('Configure render settings') and lists some allowed values, which helps distinguish it from get_render_settings (get vs set) and render_image (rendering vs configuring). However, it could be more specific about which render settings are covered.

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 vs alternatives like render_image or get_render_settings. No mention of prerequisites, ordering, or typical workflows.

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