set_world_background

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states 'Set Background shader color/strength' without explaining whether this creates a new background node, modifies an existing one, or overwrites all other background properties. It also does not mention any prerequisites, side effects, or the fact that the world must exist. This is a significant gap 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?

The description is a single, concise sentence with no filler. It front-loads the action and resource, and every word contributes to meaning. This is an example of efficient writing.

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 simple tool, the description is incomplete. An agent needs more details: whether color expects normalized RGB(A) values, acceptable ranges for strength, and whether the world must exist (or be ensured) before calling. The presence of an output schema mitigates the need to describe return values, but the input semantics remain ambiguous. The defaults in the schema are hints but not documented in the description.

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 description coverage is 0%, so the description must compensate. It explicitly names both parameters (color and strength), which clarifies their purpose. However, it does not explain the expected format (e.g., color as an array of four floats, strength as a scalar) or any valid ranges. The defaults in the schema hint at RGBA and a float, but the description itself adds minimal semantic value beyond the parameter names.

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 clear action (Set), a specific target (Background shader on the world), and the attributes being changed (color/strength). This clearly distinguishes it from siblings like set_hdri (which sets an HDRI environment) and set_color_management (which handles color management settings). An agent can tell exactly what this tool does without needing to inspect other definitions.

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 provides no context on when to use this tool versus alternatives. It does not mention that for image-based lighting one should use set_hdri, or that set_color_management handles related but separate settings. There is no guidance on prerequisites (e.g., whether a world must exist) or scenarios where this tool is the appropriate choice. The agent is left to guess.

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