env_set_ambient

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

Annotations already declare readOnlyHint=false and destructiveHint=true, covering the safety profile. The description adds the useful behavioral scope 'affects all unlit areas,' but it does not describe additional side effects or prerequisites. This is adequate for a simple setter.

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 two short bilingual sentences, front-loaded with the action and effect, and each sentence earns its place. There is no filler or redundant information.

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 single-parameter setter with a well-covered schema and clear annotations, the description fully covers purpose, effect, and accepted input formats. No output schema is needed for a setter, and nothing required to invoke the tool correctly is missing.

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 100%, and the description repeats the same accepted formats ([r,g,b] or '#RRGGBB') already present in the schema's parameter description. It clarifies that a string is acceptable despite the array type, but it adds no new meaning beyond the schema.

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 a specific verb and resource: 'set the ambient light colour' with the effect 'fills unlit areas.' This is enough to distinguish it from related siblings like env_set_background_color or env_set_background_map.

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 via its clear purpose and effect but provides no explicit when-to-use guidance or alternatives. Closely related env_set_* siblings exist, so a sentence pointing to when to choose ambient light over background/exposure would improve this dimension.

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