set_world_lighting

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

No annotations are provided, so the description must carry the burden. It states the primary actions (set color/intensity or load HDRI) but does not disclose side effects such as overwriting existing settings, validation requirements, or error behavior. It is adequate but not rich.

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 that front-loads the main purpose and includes a parenthetical note for rotation. It avoids unnecessary detail and is well-structured for quick comprehension.

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?

Given the simplicity of the parameters, the description still omits important context: whether color and hdri_path are mutually exclusive, what the rotation array represents (beyond 'Mapping rotation'), and expected value ranges. There is no mention of outputs or side effects, making it incomplete.

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% (no parameter descriptions), and the description only vaguely mentions 'background color/intensity, or load HDRI'. It does not clarify the expected format of the color array, range of strength, or requirements for hdri_path. This is insufficiently detailed for reliable use.

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 clearly states the tool sets world lighting by adjusting background color/intensity or loading an HDRI, with rotation specified for mapping. It is specific about the resource (world light) and the action (setting it), and the context distinguishes it from other lighting-related tools.

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 implies usage (setting world light properties) but does not explicitly mention when to use it versus alternatives like create_light or set_light. It lacks explicit conditions or comparative guidance, so it meets the minimum viable level but no more.

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