停止 SSH 隧道

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

The description adds the useful scope '当前 MCP 进程中的' (current MCP process), which is beyond what the annotations convey. However, it does not disclose side effects such as disconnecting active sessions or behavior when the tunnel is already stopped; the non-read-only and non-idempotent hints are already present in annotations.

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, focused sentence with no filler and front-loads the action. It is appropriately concise, though the terseness leaves some behavioral details unaddressed.

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?

For a simple stop operation with annotations and an output schema, the description covers the core action and process scope. However, it omits practical details like how to obtain the tunnel_id or what the stopping action implies for existing connections, so an agent may need to infer these from sibling tool 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?

The description only mentions '指定的隧道' (specified tunnel) and does not explain the tunnel_id parameter, its source, or how it should be formatted. With 0% schema description coverage, the agent receives no additional meaning beyond the bare string type in the input schema.

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 stops a specified SSH tunnel within the current MCP process, using a specific verb and resource. This distinguishes it from sibling tools like ssh_tunnel_start and ssh_tunnel_list, which are naturally associated with start and list operations.

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 deciding between stopping, starting, or listing tunnels. It also does not mention prerequisites like having an active tunnel or any exclusions.

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