set_render_settings

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

With no annotations, the description carries the full burden and does not disclose key behavior: what happens when a parameter is omitted (all four default to null – are they left unchanged or reset?), whether settings persist, or whether a re-render is required to take effect. It also omits any note about state mutation of the open scene. It only communicates the conceptual effect of the fields, not the operational behavior.

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 well-formed sentence with the primary choice (engine) front-loaded followed by the two size/sample settings. No redundant clauses, though it could be split for scannability.

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 four-parameter scene-mutating tool with zero annotation and zero schema-description coverage, the description covers what each field means but not the default/no-op semantics or the relationship to rendering siblings. It is adequate to attempt a call but not complete enough to predict the outcome confidently.

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, and it partially does: it identifies engine values with tradeoffs, that width/height are in pixels, and that samples is a sample count. However, it says nothing about valid ranges for width/height/samples or what null/default means for any of the four parameters, leaving a real gap.

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?

States a specific verb ('choose'/'set') and the exact resources it configures: engine, output size in pixels, and sample count. The parenthetical tradeoff (EEVEE fast, CYCLES photoreal) makes the effect concrete. It does not explicitly distinguish itself from the sibling render_image, so it falls short of a 5.

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?

Usage is only implied: an agent can infer this configures the scene before rendering, but the description never says when to call it versus render_image or execute_blender_python, nor whether it must precede a render. No exclusions or prerequisites are given.

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