set_sunset_temperature

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

With no annotations, the description takes full responsibility. It discloses the temporary nature of the setting and explains the meaning of the Kelvin parameter (lower=warmer, higher=cooler). It does not mention potential side effects or prerequisites, but the key behavioral trait is covered.

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 sentences long, each serving a clear purpose: first explaining the action and parameter, second explaining the temporal behavior. No redundancy, well front-loaded.

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 one-parameter tool with no output schema, the description covers the action, parameter semantics, and behavior (temporary override). It doesn't mention error handling or preconditions, but given the simplicity, it is sufficiently complete.

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?

The description adds significant semantic value to the single parameter 'kelvin' beyond the schema's minimal description. It explains the range implications (2500-4000 for blue-light filter, 6500 for neutral daylight), which is crucial for correct usage.

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 the color temperature of hyprsunset, specifying the resource (hyprsunset) and the action (set). It explains the meaning of Kelvin values and distinguishes the scope (temporary override), differentiating it from sibling tools like set_sunset_gamma or disable_sunset_filter.

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 provides context that the override is temporary and will be replaced by the next scheduled profile, implying it's for temporary adjustments. However, it does not explicitly mention when not to use this tool or direct alternatives like set_sunset_gamma or reset_sunset.

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