ssh_exec

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

No annotations are present, so the description carries the full burden of behavioral disclosure. It only says 'Execute a shell command', without noting that arbitrary remote commands may be destructive, that a key or authentication setup is typically required, or how output and errors are returned. This is a significant transparency gap for an SSH execution tool.

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, front-loaded sentence that directly states the core action. It earns its place, though it could have used additional structure to add usage guidance without losing brevity.

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 that this is a powerful command-execution tool with no annotations, no output schema, and a closely related sibling, the description is too thin. It omits return behavior, side-effect expectations, key/authentication prerequisites, and the relationship to ssh_sudo_exec, leaving important operational context unspecified.

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 schema description coverage is 100%, so the input schema already documents all six parameters well. The tool description adds no additional parameter-level meaning, but because the schema carries the burden, the baseline score of 3 is appropriate.

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 states a specific verb ('Execute'), a well-defined resource ('a shell command on a remote host'), and the transport mechanism ('via SSH'). It is clear and unambiguous, but it does not explicitly distinguish itself from the sibling tool ssh_sudo_exec, so it stops short of a 5.

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?

There is no guidance about when to use ssh_exec versus ssh_sudo_exec, nor any mention of when elevated privileges would be required. The existence of the sibling tool makes this omission noticeable; an agent is left to infer the distinction.

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