render_set

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the safety profile is covered and the bar is lower. The description adds nothing about whether settings are merged with existing values or fully replaced, whether changes persist across sessions, or whether a render must be idle — the behavioral questions that actually matter for a mutation tool.

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 front-loaded sentence with the verb and setting groups first, then the example payloads. The JSON samples earn their space given the empty schema, though "videos (same keys)" is a compression that costs clarity.

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?

An output schema exists so return values need not be described, and annotations cover the safety profile. Still, for a three-parameter mutation tool with completely undocumented object payloads, the definition leaves an agent unsure whether omitted keys are preserved or reset, which is essential before calling it.

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% and all three parameters are bare `additionalProperties: true` objects, so the description is the only source of key names — and it does supply concrete example keys (renderer, rayTraceBounces, width, height, samples, transparency). However, "videos (same keys)" is ambiguous about whether every image key truly applies, and no key semantics or mutation-vs-replace behavior is explained.

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 ("Change") and resource ("render settings") and enumerates the three settable groups (options, images, videos), so the agent knows exactly what the tool mutates. It does not explicitly contrast itself with render_set_cameras or render_set_passes, which sit in the same namespace and could be confused with it.

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 statement of when to use this versus render_get, render_set_cameras, render_set_passes, or render_image(s)/videos. The only signal is the name itself, which is weaker than naming the sibling tools to route to.

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