blender_render_set_engine

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 restates that the engine is set, without explaining side effects, prerequisites like an active scene, or persistence of the setting across renders. For a mutating tool, this is minimal transparency.

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 sentence with no filler, front-loading the core action. Every word earns its place, and nothing extraneous is included.

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 one-parameter setter, the schema plus description provides enough information to invoke the tool correctly. However, the absence of usage guidance and any behavioral context leaves the description slightly incomplete for an agent that needs to know why or when this affects rendering.

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?

The input schema already provides 100% coverage, including an enum of valid engine values and a description for the engine parameter. The tool description adds no additional parameter context, but none is strictly needed given the schema's completeness.

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 states a specific verb ('Set') and resource ('render engine'), making the tool's purpose immediately clear. It does not explicitly differentiate from siblings like blender_render_set_resolution or blender_render_image, but the focus on the engine setting is distinct enough.

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 gives no guidance on when to use this tool, such as setting the engine before rendering, or when an alternative would be more appropriate. The agent must infer usage purely from the tool name and sibling context.

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