ssh_tunnel_create

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

No annotations are provided, so the description carries the full burden. It states the tool creates tunnels but does not disclose success behavior, persistence, required permissions, or potential side effects (e.g., whether it starts a background process). This is a significant gap for a creation 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 a single sentence that front-loads the purpose. It is concise, but the brevity comes at the cost of omitting useful usage and behavioral information. Still, it meets the minimum for conciseness.

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 6 parameters, no output schema, and no annotations, the description is insufficient. It does not explain return values, error conditions, or prerequisites (e.g., server reachability). The sibling tools indicate a complex environment, but this tool's description lacks completeness.

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 100% with clear descriptions for each parameter. The tool description adds no additional semantic value beyond the schema, which already explains the tunnel type (local/remote/dynamic) and required ports. Baseline score of 3 is appropriate.

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 SSH tunnels, including port forwarding and SOCKS proxy. It uses a specific verb ('Create') and resource ('SSH tunnel'), and distinguishes from sibling tools like 'ssh_tunnel_close' and 'ssh_tunnel_list'.

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 alternatives (e.g., when to use local vs remote vs dynamic tunnel types, or when to use other connection tools like ssh_session_start). The siblings suggest a networking context, but no exclusions or context are given.

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