ssh_connect

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

No annotations provided, so description must fully convey behavior. It states connection establishment and session ID return but omits details like connection timeout, authentication method priority when multiple are provided, or any side effects other than opening a connection.

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?

Two focused sentences with no superfluous information. Front-loaded with purpose, immediately followed by key output (session ID). Every word earns its place.

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?

Tool has 7 parameters including complex authentication choices (password vs privateKey vs privateKeyPath) and no output schema. Description does not clarify authentication precedence, return value format, or error conditions, leaving significant gaps for agent decision-making.

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%, adequately explaining parameters. Tool description adds no extra meaning beyond what's already in schema definitions. Baseline 3 is appropriate given high schema coverage.

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 'Establish', the resource 'SSH connection to a remote server', and the output 'Returns a session ID'. It distinguishes from sibling tools like ssh_exec, ssh_disconnect, etc., which handle post-connection 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 on when to use this tool vs alternatives. Does not mention prerequisites (e.g., must have credentials) or when not to use (e.g., if you only need file transfer via SFTP). Sibling tools like sftp_upload are distinct but no comparative context.

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