ssh_tunnel_create

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

With no annotations, the description offers minimal behavioral info. It implies a mutation action but lacks details on destructive potential, authentication needs, or side effects. Simply stating 'Create SSH tunnel' is insufficient.

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 brief but under-specified. It is front-loaded but sacrifices necessary details, making it less useful despite its brevity.

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 complexity (6 parameters, no output schema), the description fails to cover typical use cases, return values, or prerequisites. It is inadequate for an agent to fully understand tool 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?

Schema coverage is 100%, so baseline is 3. The description adds no meaning beyond the schema; the generic phrase 'port forwarding or SOCKS proxy' does not clarify parameter usage or constraints.

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 SSH tunnel') and specifies types ('port forwarding or SOCKS proxy'), distinguishing it 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?

No guidance is provided on when to use this tool versus alternatives like ssh_tunnel_close or other SSH tools. There is no mention of prerequisites or contextual advice.

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