activate_scene

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

With no annotations, the description carries the full behavioral burden. 'Activate' implies a state-mutating operation affecting lights, but the description never states the side effects, whether it overrides current settings, permission requirements, or reversibility. The useful behavioral context (fade timing, sunset dimming) lives in the schema, not the description.

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?

A single front-loaded sentence with zero filler. It is efficient, though its brevity reflects under-specification rather than disciplined concision.

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 state-mutating tool with no annotations and no stated side effects, one sentence is insufficient. An output schema exists so return values need not be explained, but the description omits essential behavioral context an agent needs (what activation changes, interaction with current light state).

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 75%, so three of four parameters are already documented in the schema (room disambiguation, dynamic color cycling, transition_seconds fading). The description adds nothing beyond the generic 'saved scene', so the baseline of 3 applies.

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 states a clear verb ('Activate') and resource ('saved scene'), which implicitly distinguishes it from the sibling create_scene (the scene must already exist). However, it does not explicitly name alternatives or contrast with set_lights/set_effect, so it falls short of full sibling differentiation.

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 explicit guidance on when to use this tool versus create_scene, set_effect, or set_lights. The word 'saved' weakly implies the scene must already exist, but no conditions, prerequisites, or alternatives are stated.

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