createTunnel

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

With no annotations, description should disclose side effects and lifecycle. It only states creation, omitting that the tunnel persists until closed, potential port conflicts, or that it runs in background.

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?

Extremely concise (6 words) but insufficient for a 5-parameter tool. Sacrifices necessary detail for 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?

Incomplete for complexity: no output schema, no annotations, 5 parameters unexplained. Absent information about success indicators, errors, or what happens after creation.

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 description coverage is 0%, yet the description adds no parameter information. Even basic explanations for connectionId, localPort, remoteHost, remotePort are missing, forcing agents to infer from names.

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 'Creates' and the resource 'SSH tunnel' with parenthetical detail 'port forwarding'. It distinguishes from siblings like closeTunnel and listTunnels.

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 on when to use this tool versus alternatives. Does not mention prerequisites (e.g., need an existing connection) or instructions to use closeTunnel to tear down.

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