vyos_reset

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

Annotations already declare destructiveHint=true and readOnlyHint=false. The description adds context that it resets runtime state only, not saved configuration, and provides examples of what gets reset. This complements the annotations well without contradicting them.

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 concise and well-structured with clear sections (Args, Returns, Examples). Every sentence adds value, and the examples are immediately useful. No 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?

Given the tool's complexity and the presence of an output schema, the description covers all necessary aspects: purpose, parameters, return type, and behavioral notes. The examples make it clear how to use the tool for common tasks.

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 schema has 0% description coverage (the PathInput description is included but not the parameter itself). The description explains 'params: path — reset command path segments' and gives multiple examples that clarify how to form the path for different resets. This adds significant meaning beyond the schema.

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 it runs a VyOS 'reset' command, specifies that it resets protocol sessions, counters, or runtime state, and explicitly distinguishes from saved configuration. This differentiates it from sibling tools like vyos_set, vyos_delete, etc.

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 provides concrete examples (BGP peer, all BGP, OSPF, counters) and notes that it does not affect saved config. However, it does not explicitly state when not to use it or compare with alternatives like vyos_delete or vyos_configure_batch. The examples give clear guidance on typical use cases.

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