set_temperature

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

No annotations are provided, so the description carries the full burden. It does not disclose whether the change is applied atomically across multiple bulbs, what happens to brightness when omitted, whether the setting persists across power cycles, or what errors look like for unreachable bulbs.

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?

One short sentence, front-loaded with the verb and resource, with no wasted words. Nothing extraneous to trim.

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 mutation tool with no annotations and no output schema, the definition is minimally viable: it says what changes but not the effect on omitted parameters, multi-bulb failure behavior, or confirmation of success. The schema covers inputs fully, so the gap is behavioral rather than structural.

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%, so the schema already documents target, temp range, and brightness. The description's only parameter-adjacent content ('warm to cool white') duplicates the Kelvin endpoints already spelled out in the temp property.

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?

Specific verb+resource ('Set the color temperature of one or more WiZ bulbs') with the scope of valid values parenthetically stated. It is clearly distinguishable from the sibling set_color, which handles color rather than white-point temperature.

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 purpose implies when it is used (white-temperature control) but there is no explicit when/when-not guidance and the sibling set_color is never named or contrasted. An agent must infer that color temperature and color are mutually exclusive operations.

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