ssh_execute

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

Without any annotations, the description fails to disclose key behaviors such as synchronous execution, return format (stdout, stderr, exit code), error handling, or potential side effects. The only additional behavioral note is about AcceptEnv for environment variables.

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 front-loaded with a clear purpose sentence but becomes verbose with example code and configuration JSON. While structured, it includes redundant information that could be shorter.

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 lack of output schema, the description does not explain return values or error scenarios. It also misses prerequisites beyond configuration, such as the need for SSH to be enabled. For a tool with multiple siblings, this is a significant gap.

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 description adds value beyond the input schema by providing an example usage and a note about SSH server configuration for the env parameter. The schema already has 100% coverage, and the description clarifies each parameter's role, especially connectionId with a clear definition.

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 on a remote host via SSH'), providing a specific verb and resource. However, it does not explicitly differentiate from sibling tools like execute_command (which may be local), leaving some ambiguity about when to use this tool.

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?

No explicit guidance on when to use this tool versus alternatives. The description implies SSH connection must be pre-configured but does not state prerequisites or scenarios where other tools are preferred.

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