set_wan_web_access

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

No annotations are provided, so the description carries the full disclosure burden. It states the toggle action but does not mention security implications, persistence, authentication requirements, or impact on existing admin sessions—important for a WAN-exposure control.

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?

One short, front-loaded sentence with parenthetical clarification. No redundant content.

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 one-boolean setter with an output schema, the description and schema are largely sufficient. It lacks only security/usage context, which keeps it from being a 5.

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?

Input schema is fully self-descriptive (100% coverage) with a clear boolean 'enabled' explanation. The description adds no further parameter detail, so the baseline 3 applies.

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?

Description uses a clear verb (开启/关闭) and specific resource (外网 Web 访问), with parenthetical clarification that this controls access to the router admin UI from the WAN. This meaningfully distinguishes it from sibling tools like set_web_ports and get_remote_access_config.

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 intended use is implied: toggling external web access. However, there is no explicit guidance on when to choose this over related tools, nor any mention of prerequisites or security caveats.

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