pivot_socat_forward

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It fails to mention whether the forward is persistent, requires special privileges, or modifies system state, and only names the utility without explaining side effects or lifecycle.

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 brief, but this is under-specification rather than effective conciseness. A useful description could be expanded to one or two sentences with a clear action and context while remaining concise.

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 has no annotations, no output schema, and no contextual details in the description. For a pivot tool with three parameters and a clear use case among many sibling pivoting tools, this is severely inadequate for an agent to understand the tool's role and invocation.

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 input schema has three parameters (listen_port, target_host, target_port) with no descriptions, and schema description coverage is 0%. The tool description does not compensate by explaining what any of these parameters mean or how they relate to the port forward.

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 'Socat port forward' is a noun phrase that essentially restates the tool name without adding a specific action or scope. It does not clarify what type of port forward is created, its direction, or how it differs from sibling pivot tools like pivot_chisel_client or pivot_ssh_local.

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. There is no mention of scenarios, prerequisites, or alternatives, leaving the agent with no basis to select this tool over others.

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