automations_set_scene_config

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

No annotations are provided, so the description carries the full burden. It discloses the auto-reload behavior and provides the entities format with brightness range, but fails to mention permissions, what happens on overwrite, return values, or potential side effects like impact on active scenes.

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 concise: one sentence for purpose and action, then a clear block for entities format. There is no fluff, though it could be more structured with sections.

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?

Given zero annotations and a complex object parameter, the description omits important context: what happens when scene_id is new vs existing, any prerequisites, error conditions, and the return value (though output schema exists). The tool's behavior around overwrite and reload is only partially explained.

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 clarify parameters. It provides a detailed format and example for the entities object with brightness mapping, but does not add semantics for scene_id or name (e.g., length limits, uniqueness rules).

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 'Create or overwrite a scene config', using a specific verb and resource. It also mentions auto-reloading scenes, which distinguishes it from related tools like automations_activate_scene or automations_get_scene_config.

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 lacks any guidance on when to use this tool vs alternatives (e.g., automations_activate_scene for activation, automations_get_scene_config for reading). It does not specify prerequisites, nor when not to use it.

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