pivot_socat_forward

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

No annotations are provided, so the description carries full burden. It only states 'create a port forward' but does not disclose key behaviors like background execution, persistence, or cleanup. This is insufficient for a tool that modifies network state.

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 extremely concise, with a single sentence stating purpose followed by a clear list of arguments. No wasted words.

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?

An output schema exists but is not shown; description does not mention return behavior. While parameter coverage is decent, the tool lacks behavioral details about the port forward's lifecycle, which is critical for a network manipulation tool.

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 coverage is 0%, but the Args block in the description explains the meaning of each parameter (listen_port, target_host, target_port, protocol). This adds significant value beyond the schema's type-only definitions.

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 tool creates a socat port forward with a specific verb and resource. However, it does not differentiate from sibling pivot tools like pivot_chisel_client or pivot_ssh_dynamic, which perform similar network forwarding tasks.

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 (e.g., chisel, SSH tunnels). No prerequisites or context for its use in a pivot scenario are provided.

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