momentary_off_on_single

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

With no annotations provided, the description carries the full burden of disclosing behavior. It explicitly states the state transition: starting from a disconnected relay, closing it for the specified time, then automatically opening and restoring. This accurately describes the tool's side effects on the relay state. It does not mention peripheral concerns like prerequisites (e.g., connection) or return values, but the core behavior is transparent and predictable.

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 highly concise: a single compound sentence that front-loads the core function, then adds a behavior explanation, a relatable analogy, and a brief parameter list. Every element serves a purpose without redundancy or fluff. It is appropriately sized for a simple control tool.

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?

Given the tool's simple nature, the rich parameter schema, and the absence of an output schema, the description is comprehensively complete. It explains what the tool does, how it behaves, and what each parameter represents. The only lack is explicit coverage of unit or zero-value behavior, but these are already documented in the schema, so the description does not need to repeat them.

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%, with each parameter having a description that explains its meaning, range, and special values (e.g., time=0 disables). The tool description adds minimal value beyond the schema by merely re-listing parameter names and clarifying 'channel=回路号'. Since the schema already provides full semantics, a 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 opens with '单路点动 OFF→ON' (single-channel momentary OFF→ON), which clearly states the verb (point/trigger), resource (relay channel), and direction (OFF→ON), distinguishing it from siblings like momentary_on_off_single and multi-channel variants. It further explains the exact behavior: the disconnected relay closes for a specified time then automatically opens and restores, with the analogy of a button press, making the purpose unmistakable.

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 clear context for when to use this tool: it is for generating a momentary pulse on a relay, equivalent to pressing and releasing a button. It does not explicitly name alternatives or when not to use it, but the behavior and direction (OFF→ON) strongly imply the distinction from the ON→OFF variant, giving clear situational context without formal exclusions.

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