get_vpn

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

With no annotations provided, the description carries the full burden of disclosing behavior. It states the tool gets a list but does not mention whether it is read-only, requires authentication, or has side effects. The list of error codes hints at potential failures but does not explain behavior beyond that.

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 very short with two lines: one for purpose and one for error codes. It is concise and gets to the point, though the error codes list feels arbitrary and could be better structured elsewhere. Still, it avoids verbosity.

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 simple tool (no parameters) and presence of an output schema, the description does not provide enough context about the returned data, such as what fields are included or how to interpret the list. The error codes are partial and not fully explained, leaving gaps for an AI agent.

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?

There are no parameters, so the schema is trivially covered. The description adds no meaning beyond the schema, as it does not elaborate on what the list contains or how it is filtered. Baseline score of 3 is appropriate.

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 the verb 'Get' and the resource 'list of VPNServer', indicating a list retrieval operation. However, it does not differentiate from sibling tools like get_vpn_client_config or get_vpn_connection, which could cause confusion for an AI agent selecting the right tool.

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?

There is no guidance on when to use this tool versus alternatives such as get_vpn_client_config or get_vpn_connection. The agent is left to infer from the tool name and parent context, which is insufficient for clear decision-making.

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