ssh_execute

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

No annotations are present, so the description must carry the full behavioral burden. It does reveal two useful traits: the tool is disabled behind an environment variable, and it will create a connection on demand. But it omits critical behavior for a remote-execution tool: authentication handling, return/output format, connection cleanup, and the potential side effects of arbitrary commands.

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 compact and contains no filler; the disabled-state warning is operationally important. The purpose is front-loaded and the auto-connection note earns its place. It could be slightly better structured, but it is appropriately concise.

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 an SSH command-execution tool with no output schema and no annotations, the description is too sparse. It does not explain what the tool returns, how credentials are provided beyond a password field, or what security implications an agent should consider. An agent selecting and invoking this tool would be guessing about important runtime behavior.

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 provides descriptions for host, port, command, timeout, and password, so the description does not need to repeat those details. However, username is listed as required but missing from the properties block entirely, and the description adds no clarification for it. Overall the description adds little parameter meaning beyond what the schema already contains.

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 action ('Execute a command') on a specific resource ('a remote host via SSH'). It is clearly distinct from sibling tools like ssh_connect and ssh_disconnect, which handle connection lifecycle, and execute_local_command, which targets the local machine. The additional note about auto-creating a connection further defines its scope.

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 main use case is strongly implied: use this when you need to run a command on a remote system over SSH. The line 'Will create connection if not exists' also hints that a separate ssh_connect call may be unnecessary. However, it never explicitly names alternatives or states when this tool should not be used.

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