remote-ssh-mcp

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states the basic action but lacks critical details: it doesn't mention whether this is a read-only or destructive operation (executing commands can modify remote systems), what happens on timeout (e.g., process termination), how output is returned (since no output schema exists), or error handling. For a command execution tool with zero annotation coverage, this leaves significant behavioral gaps.

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, efficient sentence that directly states the tool's purpose without unnecessary words. It's front-loaded with the core action and resource, making it easy to parse. Every word earns its place, with no redundancy or fluff.

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 complexity of SSH command execution (potentially destructive, requires session management), no annotations, and no output schema, the description is incomplete. It doesn't address critical context like return values (stdout/stderr), error conditions, security implications, or how it relates to sibling tools (e.g., ssh_connect as prerequisite). For a tool with 4 parameters and significant behavioral implications, this minimal description is inadequate.

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 all parameters are documented in the schema itself. The description adds no additional parameter semantics beyond what's in the schema (e.g., it doesn't clarify command syntax, timeout implications, or background behavior). This meets the baseline for high schema coverage but doesn't enhance understanding.

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 ('Execute a command') and target resource ('on a connected SSH session'), making the purpose immediately understandable. It doesn't explicitly distinguish from siblings like ssh_read_buffer (which reads output) or scp_download/upload (file transfer), but the verb 'execute' is specific enough to imply command execution rather than other SSH 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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., requires an established session via ssh_connect), when to prefer background execution, or when other tools like ssh_read_buffer might be more appropriate for reading output. The agent must infer usage from the tool name and parameters alone.

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