vpn_remote

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

With no annotations provided, the description must disclose behavioral traits. It only mentions 'read-only', which implies a non-mutating operation, but it fails to describe what data is returned, whether any authentication is needed, or any other side effects. This is insufficient for an agent to understand the tool's behavior.

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 exceedingly brief, but brevity here is under-specification rather than effective conciseness. It front-loads minimal info and lacks essential context, so the single phrase does not earn its place as a complete description.

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?

For a tool with no parameters and no output schema, the description should at least clarify the nature of the returned information. 'Remote VPN users' is ambiguous – does it return a list, status, count, or something else? Given the low complexity, the description could easily have been complete, but it is not.

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 tool has zero parameters and the schema is fully covered (100% coverage). There is nothing to explain about parameters, so the description need not add anything. Baseline of 4 for zero parameters is appropriate; the description does not detract.

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 'Remote VPN users (read-only)' essentially restates the tool name with the addition of 'read-only'. It lacks a clear verb indicating what action is performed (list, view, get). It does not distinguish from sibling tools like vpn_list or vpn_graph, leaving ambiguity about what specific aspect of remote VPN users is exposed.

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 guidance is provided on when to use this tool versus alternatives. Given the large set of sibling vpn_* tools, the description offers no exclusions, comparison, or context to help an agent choose this tool correctly.

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