Switch scene

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the mutation risk is known. The description adds the command semantics (On/Off/Toggle) and the idx preference, but doesn't disclose side effects like what happens to devices in the scene or whether Toggle is state-dependent. No contradiction with annotations.

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?

Three short sentences with no filler. The core action and command values are front-loaded, and the idx preference is stated early. The cross-ref is terse but informative.

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 3-param tool with full schema coverage and an output schema, the description is mostly adequate. However, it doesn't explain the relationship between idx and name (e.g., what happens if both are provided), nor the behavioral difference between scenes and groups, which could matter for an agent deciding to call this tool.

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 100%, so the schema already documents all three parameters. The description adds the preference for idx over name, which is useful, but doesn't add meaning beyond what the schema provides for command or name.

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 specific verb ('Activate') and resource ('scene'), and the command values On/Off/Toggle clarify the action. It doesn't explicitly distinguish from sibling tools like toggle_switch or set_switch_state, but the scene focus is clear enough.

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 implies usage for scenes and mentions 'Preferred: idx' as a selection hint, but it doesn't explicitly say when to use this tool vs alternatives like toggle_switch or set_switch_state. The cross-ref to domoticz://scenes hints at context but doesn't provide exclusions.

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