shelly_switch_toggle

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

With no annotations, the description carries the full behavioral burden and does add two useful facts: it returns the post-action ChannelState and the action is audit-logged. However, it omits auth/permission requirements, whether toggling is idempotent, and what happens if the device is unreachable — real gaps for a mutation tool.

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, front-loaded sentences with no filler; the action leads and the supplementary facts follow. Appropriately sized for a simple toggle operation.

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?

An output schema exists, so return-value detail is largely redundant, and the audit-log note is welcome context. But with zero annotation coverage and zero schema description coverage, the missing parameter semantics and alternative guidance leave the definition thin for a mutation 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 0%, so the description must explain both parameters. It only hints at the channel concept via 'switch/relay channel' and says nothing about the required 'device' parameter or the channel default of 0, leaving the required param undocumented.

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?

States a specific verb (toggle) and resource (switch/relay channel), so the action is unambiguous. It does not explicitly contrast with the shelly_switch_set sibling, but the toggle-vs-set distinction is clear enough for an agent to pick correctly.

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?

No when-to-use guidance and no mention of the obvious alternative shelly_switch_set. The agent must infer that 'toggle' means flip-current-state rather than set an explicit state, which is the key selection decision here.

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