router_set_led_night_mode

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

With no annotations, the description carries full behavioral burden. It does add real value by disclosing that `force` bypasses a 'Network Guard safety check', a non-obvious safety gate, but it omits key behavioral facts: whether disabling removes the schedule or merely pauses it, whether settings persist across reboot, and whether midnight-spanning windows are handled. An output schema exists, so return values need not be covered.

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 purpose is front-loaded in one sentence, followed by a compact Args block with no filler. The argument restatements overlap somewhat with schema titles but consistently add meaning rather than duplicating types.

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 4-parameter mutation tool with no annotations and an output schema, the description covers purpose and parameters adequately but leaves behavioral questions unresolved — notably what `enable: false` does to an existing schedule and how overnight windows are interpreted. Enough to call it, not enough to predict its effects confidently.

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 compensate, and it largely does: each of the four parameters is documented, including 'HH:MM' format with concrete examples, the direction of each boundary (start = LEDs off, end = LEDs back on), and the meaning of `force`. It stops short of stating defaults for start_time/end_time (they live in the schema only) or what start_time/end_time do when `enable` is false.

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 first sentence gives a specific verb (configures) plus resource (night mode for router front panel LEDs) and states the effect (LEDs turned off automatically during sleeping hours). It is clearly distinguishable from read-side siblings such as router_get_led_status, though it does not name any sibling explicitly.

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?

Usage is only implied: the enable/start_time/end_time semantics make the scheduling intent obvious, but there is no explicit statement of when to use this versus router_get_led_status or other LED controls, and no when-not guidance. The `force` note hints at a prerequisite (Network Guard) without explaining when bypassing is appropriate.

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