ssh_start_interactive

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

With no annotations, the description must fully disclose behavior, but it only states 'start interactive session'. It does not explain that a session is created and must be managed (e.g., sending input via ssh_send_input or terminating via ssh_terminate_interactive), nor does it mention side effects or required prior state.

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, clear sentence with no extraneous words. It is front-loaded with the core purpose, though for a complex tool it may be too brief.

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?

No output schema is provided, and the description fails to explain what the tool returns (e.g., session ID, success indicator). It also doesn't clarify prerequisites, such as needing an existing SSH connection (implied by connection_id parameter). For a tool that manages interactive sessions, this is incomplete.

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 covers 100% of parameters with descriptions. The description adds no extra meaning beyond the schema; it mentions 'interactive commands' which aligns with the command parameter but does not elaborate on pty settings.

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 tool starts an interactive SSH session and provides examples (sudo, vim, mysql) that indicate its purpose. It distinguishes from sibling tools like ssh_execute which is for non-interactive commands, though it doesn't explicitly name alternatives.

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 gives examples of interactive commands but does not provide explicit guidance on when to use this tool versus alternatives like ssh_execute or ssh_start_async_command. No when-not-to-use or prerequisites are mentioned.

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