mcp_ssh_mcp_createTerminalSession

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

No annotations are provided, so the description must convey behavioral traits. It only states 'creates' without disclosing side effects, initialization behavior, or whether it requires prior authentication. Important details like session lifecycle, resource limits, or impact on existing sessions are omitted.

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 that efficiently states the core function. It avoids unnecessary elaboration, though it might benefit from slightly more detail 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?

Given the tool's complexity (4 parameters, no output schema, many sibling tools), the description is insufficiently complete. It does not explain what the function returns, how it relates to connect or executeCommand, or what constitutes a valid interactive session. More context is needed for proper selection and use.

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?

The input schema provides zero descriptions for any of the four parameters (coverage 0%). The description does not explain the purpose or format of connectionId, rows, cols, or term. The parameter names give some hints, but the description adds no additional meaning beyond the raw schema.

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 'Creates a new interactive terminal session' clearly identifies the action (create) and resource (interactive terminal session). This distinguishes it from sibling tools like executeCommand (non-interactive) and backgroundExecute (background execution). However, it could be more explicit about what 'interactive' means in this context.

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 versus alternatives such as executeCommand or writeToTerminal. It does not mention prerequisites (e.g., an existing connection via connect) or scenarios where this tool is inappropriate (e.g., for non-interactive commands).

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