pivot_ssh_dynamic

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

With no annotations, the description must disclose behavioral traits. It does not mention that this tool creates a tunnel, runs in the background, or requires SSH connectivity. The side effects (starting a proxy on localhost, binding to a port) are implied but not explicit. The description only lists parameters without explaining the tool's operation or lifetime.

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: one sentence for purpose and a list of parameter descriptions in Args format. It is front-loaded with the key verb-noun pair. No unnecessary text.

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 presence of an output schema, return values are documented elsewhere. However, the description does not explain how the SOCKS proxy is used after creation (e.g., to route traffic through the SSH server), nor does it mention concurrency or cleanup. It is minimally sufficient but lacks important operational context.

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's parameter descriptions add value. Each parameter has a brief, functional explanation (e.g., 'SSH server to use as SOCKS proxy', 'Local SOCKS port'). However, the descriptions are minimal and do not clarify default behavior (e.g., that password is optional if key_file is provided). Score 4 would require more detail; 3 is adequate given the baseline.

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 action: 'Create an SSH dynamic SOCKS proxy.' The verb 'Create' and resource 'SSH dynamic SOCKS proxy' are specific. However, it does not differentiate from sibling tools like pivot_ssh_local or pivot_ssh_remote, leaving the agent to infer the difference from the name alone.

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_local, pivot_ssh_remote, or pivot_chisel_client. The description lacks context for appropriate use cases or prerequisites (e.g., SSH access to a machine).

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