ssh_session_command

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the action without mentioning whether the command blocks, how output is returned, potential side effects, or session requirements. This is a significant gap for a tool that executes arbitrary commands on a remote system.

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 extremely concise, but it is under-specified rather than efficiently detailed. It reads as a tautology of the tool name and does not provide useful information that earns its place. A minimal viable description would need at least a sentence of context.

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 3 parameters, no annotations, and no output schema, the description is far too incomplete. It lacks essential operational context such as session requirements, return values, error handling, and timeout semantics. The tool cannot be correctly used based on this description alone.

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 does not explain any of the three parameters (session_id, command, timeout). With 0% schema description coverage, the description must compensate but adds no meaning beyond the schema. Users get no clarity on required arguments, command format, or timeout behavior.

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 'Run SSH command' uses a verb and resource, indicating it executes commands over SSH. However, it does not specify that it operates on an existing SSH session identified by session_id, nor does it differentiate from other command execution tools like kali_exec or exec_stream. The name suggests the function, but the description alone is too generic.

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 provides no guidance on when to use this tool versus alternatives. Given many sibling tools for command execution (e.g., exec_stream, kali_exec, reverse_shell_command), there is no indication of the intended context or prerequisites such as an active session.

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