vyos_save_config

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

Annotations already indicate readOnlyHint=false (write), destructiveHint=false, idempotentHint=true, openWorldHint=true. The description adds the default path and return type but does not provide additional behavioral context such as permissions needed or side effects beyond what annotations cover.

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: two sentences covering purpose, default behavior, optional parameter, and return value. No extraneous text, every sentence serves a clear function. Structure is clean and front-loaded.

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 simplicity (one optional parameter, a clear return type, and annotations covering safety and idempotency), the description covers the essential aspects: purpose, default path, optional custom path, and return. It lacks mention of file accessibility or overwrite behavior, but these are minor given the context. Overall, fairly complete.

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 description mentions 'file — optional save path', repeating the schema's description. The schema already documents the 'file' parameter as optional with default null. With schema description coverage reported as 0%, the description adds minimal extra meaning beyond the schema, achieving only the baseline.

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 clearly states 'Save the running configuration to disk' with a specific verb and resource. This distinguishes it from siblings like vyos_load_config (load config) and vyos_show_config (show config), ensuring unambiguous purpose.

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 by describing the action (save to disk, default path, optional custom path), but does not explicitly state when to use this tool vs alternatives or when not to use it. No exclusions or alternative tool names are given, so the guidance is only implicit.

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