vyos_return_values

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

No annotations provided, description only notes it returns a list. Does not disclose read-only nature, error conditions, or permission requirements. Insufficient transparency for a tool with no annotations.

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?

Two sentences plus an args section, no wasted words. Front-loaded with main purpose and usage context.

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?

Covers purpose, usage, and parameter meaning. Lacks output format details beyond 'as a list', but sufficient for a simple getter with one parameter.

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?

Path parameter is explained with an example, adding meaning beyond schema's type-only definition. Compensates for 0% schema description coverage.

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 states verb 'Get' and resource 'values of a multi-valued VyOS config node as a list', clearly distinguishing from sibling vyos_retrieve by specifying when to use each.

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?

Explicitly says 'Use this instead of vyos_retrieve when a node has multiple values', providing clear usage context. Lacks mention of when not to use other siblings.

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