set_group_color_preset

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

Annotations already declare the operation non-read-only, non-destructive, idempotent and closed-world, so the safety profile is covered. The description adds genuinely useful behaviour context by listing the twelve accepted preset names, which the schema does not enumerate at all. It stops short of stating that the whole group is affected uniformly, that existing brightness/temperature may be overridden, or what the response confirms.

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 front-loaded sentence; the long preset list is load-bearing information rather than padding. Nothing could be removed without losing content.

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?

The tool is simple, an output schema exists so return values need no explanation, and annotations carry the safety profile. The remaining gap is target selection: with 0% schema coverage, the description should have said how a room or zone is identified when every targeting parameter is optional.

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% for three parameters, and the description only compensates for one of them: the valid values of the required 'preset' string. It never explains the group_id vs group_name pair, that group_id accepts string or integer, or what happens when both are left at their empty defaults — the riskiest ambiguity in this 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 gives a specific verb and resource ("apply a named preset") plus the target scope ("a room or zone"), which aligns with the group-oriented name. It implicitly separates itself from the light-level set_color_preset, but never names that sibling, so the differentiation relies on the agent noticing the 'group' prefix.

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?

There is no guidance on when to choose this over set_group_color, set_group_color_rgb, or set_scene, nor any note about precedence (e.g. whether a preset overrides a previously set scene or effect). Usage is only inferable from the enumeration of preset names.

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