ssh_exec

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

With no annotations, the description carries the behavioral burden well: it discloses how host is resolved via ~/.ssh/config, that password mode uses sshpass with the password only via an environment variable, and that timeout applies to the remote command. Minor gaps remain, such as stderr/exit-code handling, but the core behavior is transparent.

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 efficiently structured: a one-sentence purpose, followed by short bullets for host notes, authentication and timeout. Every sentence contributes useful information with no fluff or redundancy.

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?

For a tool with no annotations and no schema parameter documentation, the description is complete: it covers host targeting, auth paths, timeout semantics, and the shell-command/return-output model. An agent can safely construct a correct call.

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 has zero description coverage, so the description fully compensates. It explains host with two concrete formats, command as a shell command, timeout as a seconds default of 60, and password as the switch to password authentication. This adds meaning well beyond the bare 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 opens with a specific action: executing shell commands on a remote host and returning output. The 'remote host' wording differentiates it from local execution tools like exec_cmd, and the concrete host format examples make the resource unambiguous.

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?

It gives clear context for use: remote host execution with host alias or user@ip formats, default key-based or password-based auth, and a configurable timeout. It does not explicitly name sibling tools or state exclusions, but the remote-host scope is an adequate differentiator.

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