Start SSH Port Forward

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

The description adds a key behavioral trait beyond annotations: the tunnel stays alive only while the MCP server process is alive, which is crucial for lifecycle management. Annotations already flag this as non-read-only and open-world, and the description does not contradict them. It stops short of disclosing other behaviors like port conflict handling or return value.

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 only two sentences: the first front-loads the primary action, the second provides a critical lifetime detail. Every word earns its place, with no redundancy or extraneous content.

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 description covers the core action and lifetime, and the schema fills in parameter details, but it does not mention the expected return value, error conditions, or how the tunnel is stopped. Given there is no output schema, these gaps remain for the agent to infer, making it adequate but not complete.

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 covers 83% of parameters with meaningful descriptions (e.g., localPort, remotePort, host, localHost, remoteHost), leaving only connectTimeoutSeconds undocumented. The description adds no additional parameter semantics, so the schema already carries the burden; baseline 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 verb 'Start' and the resource 'local SSH -L tunnel' through the configured SSH host. This distinguishes it from sibling tools like remote_ssh_list_port_forwards and remote_ssh_stop_port_forward, making the action unambiguous.

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 does not explicitly mention alternatives or when-not-to-use scenarios, but it provides context that the tunnel remains alive only while the MCP server process is alive, implying temporary use. Sibling tool names suggest alternatives, but the description itself does not offer direct comparative guidance.

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