set_temperature

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

Explains the temperature scale (Elgato units with approximate Kelvin values), but omits behaviors like what happens if lights are off or if values are out of range. No annotations to supplement.

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 plus an Args list. Front-loaded with main purpose. Every sentence adds value, no fluff.

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?

Adequate for a simple tool with two parameters. Describes the key parameter (temperature) well. Could mention that temperature range applies per light, but not critical given sibling context.

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?

Adds significant value for the temperature parameter by providing units and mapping to Kelvin. The light_names parameter is minimally described (optional list), but the schema is sparse (0% coverage) so the description helps.

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?

Clearly states the action (set), resource (color temperature), and scope (all or specified lights). Distinct from sibling tools like set_brightness and toggle_lights.

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?

No explicit guidance on when to use this vs alternatives. The purpose is clear but lacks context like prerequisites or when to avoid usage.

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