render_set_engine

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

Goes beyond the annotations: it explains that the tool first probes candidate classes, fails with a useful error listing installed renderers, leaves scene content untouched, and may reset some render settings. This fleshes out the destructiveHint with the exact scope of the mutation and no contradiction with readOnlyHint=false.

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 compact, front-loaded with the action, and every sentence adds information (action, valid values, probing, error behavior, side effects). The bilingual repetition is the only redundancy and is acceptable.

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?

The description covers the param, failure behavior, and side effects, which is sufficient for a one-parameter setter. The only missing piece is an explicit statement of the success return value, but no output schema exists and the behavior is otherwise fully specified.

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 schema already documents the only parameter with an enum and example, and the description simply restates the same friendly names. It adds no new per-parameter semantics beyond the schema, so it earns the baseline for high schema coverage.

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 (Switch) with a precise resource (production renderer) and the exact allowed values, including the list of eight friendly names. This separates it from render_get_engine (query) and list_render_engines (list) without ambiguity.

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?

Clearly frames the operation as switching the production renderer by friendly name, giving the agent a direct trigger condition. It does not, however, name the sibling query/list tools or give a when-not-to-use rule, so it stops at clear context rather than explicit routing.

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