set_color_temp

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

No annotations are provided, so the description carries the burden. It discloses the key behavior: setting white mode and the temperature scale (0 warm, 100 cool). However, it doesn't mention what happens to the light's current color, whether the light must be on, or any side effects. The description is honest but minimal.

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?

Two sentences, front-loaded with the core action and scale. The optional brightness note is a useful addition without bloat. Every word earns its place.

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 3-parameter tool with an output schema, the description covers the essential semantics. It lacks explicit notes on edge cases (e.g., invalid percent values, behavior when brightness is null) but these are minor given the schema's defaults and the tool's simplicity.

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 0%, so the description must compensate. It explains the 'percent' parameter's meaning (0 warm, 100 cool) and that 'brightness' is optional. It doesn't explain 'device' but that's self-evident from the name and sibling context. The description adds meaningful semantics beyond the raw 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 the tool's function: setting a light to white mode at a color temperature percentage, with a specific range (0 warm, 100 cool). It also mentions an optional brightness parameter. This distinguishes it from siblings like set_color (which likely sets RGB/color) and set_brightness (which only sets brightness).

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 when to use this tool: when you want to set a light to white mode with a specific color temperature. It doesn't explicitly state when not to use it or name alternatives, but the sibling list and the clear scope (white mode + temperature) provide enough context. The optional brightness note also clarifies a combined use case.

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