momentary_off_on_multi

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

With no annotations, the description carries the burden and discloses the key behavior: selected relays engage for a specified time then auto-disconnect, while unselected bits remain unchanged. It does not cover edge cases like time=0 or error handling, but the core behavior is transparent.

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 with the main action front-loaded. It contains no filler and efficiently conveys the tool's purpose and behavior.

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 tool with four parameters and no output schema, the description combined with the schema gives adequate understanding of the operation. Minor gaps include lack of mention about return values or the meaning of time=0, but these are covered in the schema and not critical for a simple control command.

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?

All four parameters are fully described in the schema (100% coverage), so the baseline is 3. The description adds directional context (OFF→ON) and ties the mask to relay selection, but it does not significantly enhance parameter understanding beyond the schema.

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 is a multi-channel momentary OFF→ON operation with bitwise selection, and relays automatically disconnect after a specified time. This distinguishes it from single-channel and ON→OFF variants like momentary_on_off_single and momentary_on_off_multi.

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 controlling multiple relays with a timed OFF→ON action, and the name suggests it is the multi-channel counterpart to momentary_off_on_single. However, it does not explicitly state when to use this tool over alternatives or mention any exclusions.

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