ssh_connect

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Establish' is vague about what actually happens—whether it opens an interactive session, tests connectivity, persists the connection, or requires a subsequent disconnect. It does not mention session lifecycle or side effects like ControlMaster multiplexing.

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, concise sentence with no wasted words. It lacks structured detail but is appropriately sized for a simple tool statement, earning a high score for efficiency.

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?

With no annotations, no output schema, and five parameters, the description is severely incomplete. It fails to explain the return value, session persistence, how to disconnect, or the purpose of useControlMaster. For a tool that likely serves as a prerequisite for other SSH operations, far more context is needed.

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 100%, so the schema already documents all five parameters. The description adds no additional meaning about parameters beyond the schema, so the baseline score 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 'Establish an SSH connection to a remote host' uses a specific verb ('Establish') and resource ('SSH connection'), clearly indicating the tool's function. It does not explicitly differentiate from sibling tools like ssh_execute or sftp_upload, but the resource name 'connection' makes it reasonably distinct.

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 provides no guidance on when to use this tool versus alternatives like ssh_execute or sftp_upload. There is no mention of prerequisites, follow-up commands, or scenarios where this tool is preferred, leaving usage purely implied by the name.

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