List SSH Port Forwards

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

The annotations already declare readOnlyHint=true, so the description adds value by specifying the scope 'started by this MCP server process', which clarifies that it does not list system-wide or other external tunnels. This behavioral insight goes beyond the annotation and is appropriate for a simple list operation.

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 clear sentence that immediately states the action and scope. There is no redundancy or filler, making it highly efficient for an agent to parse.

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 tool's simplicity (no parameters, no output schema, read-only behavior confirmed by annotations), the description fully specifies what the tool does and its scope. No additional behavioral details are needed for correct 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 tool has zero parameters and the input schema is empty, so the baseline for this dimension is 4. The description does not need to explain parameters, and it correctly avoids adding irrelevant information.

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 uses the specific verb 'List' with the resource 'SSH tunnels' and adds a scope limitation 'started by this MCP server process', which clearly distinguishes it from sibling tools like remote_ssh_start_port_forward and remote_ssh_stop_port_forward. It fully states what the tool does and its exact domain.

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 clearly indicates this tool is for viewing tunnels created by this specific MCP server process, providing a clear context for use. While it does not explicitly name alternatives or exclusions, the sibling tool names make the usage obvious. It stops short of a 5 due to lacking explicit when-not-to-use guidance.

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