vyos_exists

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

Returns true/false in data field, but no details on error handling, permission requirements, or side effects. With no annotations, description should provide more behavioral 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?

Very concise: one line for purpose, one line for return value, one line with args format and example. No extraneous text.

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 no output schema, return value is explained. However, missing details on what happens for malformed paths or non-existent paths (e.g., returns false). Adequate but not thorough.

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?

Schema coverage is 0%, so description adds crucial meaning: explains path is a configuration path as an array of string segments, with example. Clear enough for agent to provide valid input.

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?

Clear verb 'Check', resource 'VyOS configuration path', and action 'exists'. Example provided. Distinguishes from siblings like vyos_show which likely returns actual config values.

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 explanation of when to use this tool versus alternatives such as vyos_show or vyos_validate. No context on prerequisites or when not to use it.

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