pivot_ligolo_start

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

With no annotations, the description carries the full burden of disclosing behavioral traits, but it only states a single action. It does not mention side effects, whether the proxy runs in the background, system modifications, network interactions, or any other operational details, leaving the agent completely uninformed about 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 short, but this is under-specification rather than effective conciseness. The single sentence provides minimal information and leaves significant gaps, so it does not earn its place as a useful explanatory statement.

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 two parameters, no output schema, and no annotations, this description is severely incomplete. It fails to explain what starting a Ligolo proxy does, what the parameters control, or what the expected result is, making it impossible for an agent to use the tool correctly.

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 schema has two parameters with 0% description coverage, and the description does not mention 'port' or 'interface' at all. The defaults are present but their meaning and effect are unexplained, so the description adds no value in helping an agent understand parameter semantics.

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 ligolo proxy' is essentially a restatement of the tool name 'pivot_ligolo_start' with no additional information. It identifies the verb and resource but fails to provide any context about what Ligolo is or what starting it entails, making it a tautology rather than a clarifying statement.

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 provides no guidance on when to use this tool versus the many sibling pivot tools (e.g., pivot_chisel_client, pivot_ssh_local). There is no mention of prerequisites, typical scenarios, or alternatives, so an agent cannot infer the appropriate usage context.

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