render_set_engine

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

The description discloses no behavioral traits. It does not say that the tool mutates the scene/render settings, whether the change applies immediately, or whether it affects subsequent renders; the annotations provide only a title, so the description carries the full burden and fails to carry it.

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 compact and contains no filler words, so it scores well on brevity. It is not well-structured as a complete definition, but as a concise statement it earns its place.

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?

Even for a one-parameter tool, the description is incomplete: it omits the core action of setting the render engine and gives no usage context. A minimal complete description would be something like 'Set the active render engine for the scene to CYCLES or BLENDER_EEVEE.'

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%, but the description at least names the two valid engine values, CYCLES and BLENDER_EEVEE, which the schema does not provide as an enum. However, it does not explain what the engine parameter means, what the default implies, or what effect choosing one engine has.

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 'engine: CYCLES or BLENDER_EEVEE.' only restates the parameter name and enumerates allowed values; it never states that this tool sets the render engine. The intended action must be inferred from the tool name and annotation title, rather than from the description itself.

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 about when to use this tool versus alternatives. This is especially relevant because sibling tools like render_set_settings and render_set_output could plausibly overlap with setting render engine options, but no distinction or condition is provided.

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