set_render_settings

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'Set various render settings' which implies mutation but gives no details on side effects, persistence, error behavior, or whether settings apply immediately. For a mutation tool, this is a significant gap.

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, short sentence with no unnecessary words, so it is concise. However, it is also severely under-specified; it is concise at the expense of substance. The sentence is front-loaded with the verb, but it lacks any detail that would aid an agent.

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 7 undocumented parameters and no annotations, the description is grossly insufficient. An agent would not know which settings can be changed, what values are valid, or what the tool actually does beyond the bare claim. The output schema exists but does not compensate for the lack of input 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 description coverage is 0% and the description mentions no parameters by name or meaning. All 7 properties (samples, denoiser, use_bloom, etc.) are completely undocumented in both the schema and the description. The description offers zero help in understanding what values are expected or how they map to render settings.

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 a specific verb ('Set') and resource ('render settings for the active scene'), making the tool's purpose unambiguous. It does not name sibling tools like set_render_engine or set_render_output, but the phrase 'render settings' generally covers them, so an agent can infer the scope without opening the schema.

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 siblings such as set_render_engine, set_render_output, or set_color_management. It does not mention any context, prerequisites, or exclusions. The agent is left to guess whether this tool handles all render settings or only a specific subset.

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