connect

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

No annotations are provided, so the description carries full responsibility. It does not explain behaviors such as connection failure handling, state persistence (implied by 'name' and 'rememberPassword' parameters), security implications, or whether the connection remains open. The single sentence is insufficient for a tool with side effects.

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 brief sentence, which is concise and front-loaded. However, for a tool with 9 parameters and significant behavior, it may be too terse. Still, it does not contain unnecessary words.

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?

Given the tool's complexity (9 parameters, no output schema, no annotations), the description is severely incomplete. It fails to mention return values, error conditions, or how the connection state is managed. Agents cannot effectively use this tool based solely on the description.

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?

With schema coverage at 0%, the description provides zero explanation of the 9 parameters (e.g., distinction between password and privateKey, purpose of tags, default for port). The description does not compensate for the missing schema descriptions.

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 ('Establishes') and resource ('SSH connection to a server'). It is specific and distinct from sibling tools like 'getConnection' (retrieve) and 'disconnect' (terminate). No tautology or ambiguity.

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 offers no guidance on when to use this tool, prerequisites (e.g., network access, credentials), or when to use alternatives (e.g., 'createTunnel' for tunneled connections). Agent is left uninformed about context.

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