pivot_ligolo_start

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

Annotations are absent, so the description must disclose behavioral traits. It merely states the action without any details about system effects, permissions required (e.g., root for TUN interface), background execution, or stopping the server. 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 brief and to the point, using a single sentence plus parameter list. It is front-loaded with the purpose. While minimal, it has no waste. However, the parameter list could be more integrated.

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 tool's role in pivoting, the description lacks context about its place in the workflow. It does not mention that it runs a proxy server, how it relates to sibling tools like pivot_add_pivot or pivot_stop_tunnel, or what the output schema provides. The agent is left guessing about usage patterns.

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 description coverage is 0%, so the description must add value. It specifies that 'interface' is a TUN interface name and 'port' is a listening port, providing defaults. However, it does not explain constraints (e.g., port range, interface existence) or how to use them effectively.

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 'Start' and the resource 'Ligolo-ng proxy server for pivoting.' Among many pivot siblings (e.g., pivot_chisel_client, pivot_ssh_dynamic), this tool is specifically for starting a Ligolo-ng proxy, making its purpose distinct.

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. The description does not mention prerequisites, cases where it should be used, or when not to use it. Without context, an agent cannot easily decide between this and other pivot tools.

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