momentary_on_off_single

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

No annotations are provided, so the description must disclose behavior. It states the core behavior (relay auto-disconnects after time) and gives an equivalence ('延时关闭'). However, it omits edge cases like time=0 (disabled) and broadcast address behavior, which are present in the schema but not in the description.

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?

Two concise sentences with a parameter list. The first sentence front-loads the core function; the second adds an equivalence. The parameter list is redundant but not verbose.

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 simple relay control tool with full schema coverage, the description adequately explains the main behavior but lacks edge-case and return-value context. Without annotations, some behavioral transparency is missing, but the tool is simple enough that the description is nearly sufficient.

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 covers all parameters with descriptions (100%). The description repeats param names and provides a brief mapping (channel=回路号, time=延时时间), which adds minimal semantic reinforcement but does not exceed schema detail.

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 the tool performs single-channel momentary ON→OFF: the relay engages and automatically disconnects after a specified delay. This directly distinguishes it from sibling tools like momentary_off_on_single and multi-channel variants.

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 provides context that it is a delayed shutdown for a single channel, but does not explicitly state when to use this over alternatives or mention exclusions. It relies on the name and sibling differences for differentiation.

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