zyxel_save_config

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

No annotations are provided, so the description carries the full burden. It does not disclose that saving overwrites the startup configuration, which is a potentially destructive or irreversible action, nor does it mention any confirmation behavior beyond the schema. The minimal description lacks cautionary context.

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 a single concise sentence that is front-loaded with the primary action. It contains no filler words or redundant information.

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?

The tool is simple with no output schema and one optional parameter, but the description omits any mention of prerequisites, such as an active connection (sibling tool zyxel_connect), or typical use cases. It is complete enough for basic invocation but lacks full contextual guidance.

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 already covers 100% of the single parameter and describes 'confirm' as 'Confirm the save operation.' The tool description adds no additional meaning or clarification about how the confirm parameter behaves (e.g., what happens if set to false), so the baseline score of 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?

The description 'Save running configuration to startup configuration' clearly states the tool's function with a specific verb and resource, and it distinguishes itself from sibling tools like zyxel_show_running_config and zyxel_show_startup_config. It is unambiguous and action-oriented.

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 implies usage (persisting running config after changes) but provides no explicit guidance on when to use it or alternatives. There are no similar save-tool siblings, so the need is inferred rather than stated.

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