ssh_exec

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

No annotations are provided. The description notes that commands are interpreted by the remote shell and returns stdout, stderr, and exit code. However, it does not disclose potential side effects, idempotency, or concurrency constraints.

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?

Two sentences convey the core functionality and key behavioral note without unnecessary detail. Perfectly 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?

Given 7 parameters, no output schema, and no annotations, the description covers the basic behavior but lacks detail on authentication methods, error handling, or output format expectations.

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 coverage is 100% and already includes detailed descriptions. The description only repeats 'interpreted by the remote login shell' without adding new meaning beyond the schema. With high coverage, the description adds minimal value.

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 'Execute a command on a remote host via SSH' with a specific verb and resource, and mentions shell behavior, distinguishing it from sibling tools like ssh_read_file or ssh_download.

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 implies usage for arbitrary SSH commands but does not explicitly state when to use this tool versus alternatives like ssh_multi_exec for multiple hosts or ssh_read_file for file reading.

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