reboot_router

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

The description discloses the key behavioral impact (network outage for 1-2 minutes) via an explicit warning. However, it does not explain the 'confirm' parameter's role, whether the reboot is immediate, or other side effects, and there are no annotations to fill in those gaps.

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 extremely concise, consisting of a clear action and a warning, with no filler words. It is front-loaded and every element serves a purpose, making it highly scannable.

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 mutation tool with no annotations, the description covers the main purpose and side effect but omits crucial context about the 'confirm' parameter and what happens when it's false. Given the output schema exists, return values are not required, but the confirm semantics are a significant gap.

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?

The input schema has a 'confirm' boolean with default false and no property description, and the description does not mention it at all. With schema description coverage at 0%, the description fails to compensate, leaving parameter semantics entirely unexplained.

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 explicitly states '重启路由器' (restart router), a specific verb and resource, and adds a warning about a 1-2 minute network outage, which provides valuable context. It is clearly distinguishable from the sibling tool 'restart_ap' by specifying 'router'.

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, nor any prerequisites or exclusions. The description merely states the action and its side effect, leaving the agent to infer appropriate usage.

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