Create Remote SSH Tunnel

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

The annotation indicates readOnlyHint=false, which aligns with creating a tunnel, but the description adds no behavioral details beyond that. It does not disclose potential side effects (e.g., port binding, required permissions, impact on existing tunnels). The description does not complement the 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 one short sentence, concise and to the point. It avoids unnecessary words. No structural issues, though it could be slightly expanded with usage context without becoming verbose.

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?

Despite having an output schema, the description lacks important context: it does not mention the need for an already established SSH session, potential conflicts with existing port forwards, or what happens on failure. For a non-idempotent, state-changing tool, this is insufficient.

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?

Input schema has 100% description coverage, so each parameter is already documented in the schema. The description does not add any additional meaning or context, but since schema coverage is high, a baseline of 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 action: creates a remote SSH port forward. The verb 'creates' and resource 'remote SSH port forward' are specific. It is distinguishable from sibling tools like tunnel_local_forward due to the word 'remote', though no explicit comparison is made.

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 vs alternatives (e.g., tunnel_local_forward). No mention of prerequisites like an active SSH session, which is implicitly required by the sessionId parameter. No when-not-to-use or exclusion criteria.

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