disconnect_relay

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

With no annotations, the description carries the full burden. It only mentions the action (OFF) and does not disclose prerequisites like connection setup, behavior when the device is unreachable, whether broadcast address 255 is supported, or any side effects. This leaves significant behavioral ambiguity 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?

The description is a single concise sentence that immediately conveys the action and parameter mapping. It has no redundant content and earns its place fully.

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?

Despite having clear parameter documentation in the schema, the description lacks usage context, prerequisites, or differentiation from many closely related sibling tools. The lack of annotations and output schema further compounds the gap—an agent cannot tell when to use this tool or what to expect beyond the basic operation.

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 coverage is 100%—both parameters have detailed descriptions including ranges, discovery methods, and broadcast address semantics. The description merely repeats 'address=機器地址, channel=回路號' without adding any new meaning beyond the schema, so the baseline of 3 is appropriate.

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 it '断開指定設備指定一路繼電器（OFF）'—disconnecting (turning off) a specific relay on a specific device. This uses a specific verb and resource, and distinguishes it from siblings like connect_relay (ON), all_relays_off (all relays), and group_disconnect.

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 guidance is provided on when to use this tool versus alternatives such as all_relays_off or connect_relay. The description only states what it does without any contextual selection criteria, exclusions, or references to sibling tools.

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