ligolo_tunnel_start

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

No annotations are provided, placing the full disclosure burden on the description. The description only states the basic action ('start a tunnel') without revealing behavioral traits such as required permissions (e.g., root), side effects (interface binding), or state changes. This is insufficient for safe invocation.

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 a single concise sentence of 6 words, well-suited for quick reading. However, it sacrifices some completeness for brevity, which is acceptable for a simple tool but could be slightly improved.

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?

The tool likely depends on a previously selected agent session (as hinted) and may require other setup steps (e.g., ligolo_session_select, ligolo_proxy_start). The description does not explain these dependencies, the lifecycle of the tunnel, or what constitutes a successful start. Given the lack of output schema and annotations, the description is incomplete for a user unfamiliar with the toolset.

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 single parameter 'tun' is described in the schema as 'TUN interface name to use'. The description does not add any additional meaning beyond the schema. With 100% schema coverage, the baseline is 3, and no extra value is provided.

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 'Start a tunnel through a selected agent session' clearly specifies the action (start) and resource (tunnel), and includes contextual detail ('through a selected agent session') that distinguishes it from siblings like ligolo_tunnel_stop (stop) or ligolo_session_select (select).

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 implies a dependency on a selected agent session but does not explicitly state prerequisites, when to use this versus other tunneling or session tools, or alternatives like ligolo_interface_create. Usage context is implied but not explicit.

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