pivot_ssh_local

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

With no annotations, the description must disclose behavioral traits, but it only states 'SSH local port forward.' It does not mention that a listener is created, whether the command blocks or runs in background, authentication requirements, or any side effects—critical missing information for a network tool.

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 at three words, with no wasted content. However, it is under-specified for a tool with four required parameters and no other documentation, making the brevity a drawback rather than a strength.

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 four required parameters, no annotations, and no output schema, yet the description is essentially a stub. It fails to provide any context about return values, execution behavior, when to use it, or how it fits into the larger pivot workflow, making it insufficient for reliable 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 offers no descriptions (0% coverage), and the description does not compensate. While parameter names like local_port, remote_host, remote_port, and ssh_target are somewhat self-explanatory, the description provides no additional meaning about their relationship, formatting, or purpose.

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 phrase 'SSH local port forward' clearly identifies the operation (port forwarding) and the specific variant (local vs remote/dynamic). It distinguishes from sibling tools like pivot_ssh_remote and pivot_ssh_dynamic through the word 'local', though it is not a full sentence.

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 such as pivot_ssh_remote or pivot_ssh_dynamic. There is no mention of use cases, prerequisites, or context, leaving the agent to infer from the name alone.

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