ssh_exec

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

With no annotations provided, the description carries the transparency burden. It discloses specific technical behaviors such as Base64 UTF-16LE encoding, Session 0 bypass, 8191-character limit bypass, and dual authentication, which go beyond a simple statement of purpose and provide useful context about the tool's operation.

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 a single sentence that front-loads the main purpose and then lists key capabilities in a compact manner. Every word contributes meaningful 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?

The tool is complex (9 parameters, no output schema, no annotations) and the description omits crucial information such as return values, exit codes, error handling, and authentication details beyond the vague 'dual auth.' The description does not fully equip an agent to understand the tool's complete 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?

Schema coverage is 100%, so the baseline is 3. The description enriches parameter understanding by explaining that Base64 UTF-16LE relates to command encoding and that Session 0 bypass relates to desktop session handling, adding value beyond the schema's individual parameter descriptions.

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 tool's function: 'Execute remote commands over SSH.' It distinguishes itself from siblings like file transfer and connection testing by focusing on command execution, making its purpose 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?

The description implies usage for running commands remotely but does not explicitly state when to use this tool versus alternatives. It provides no exclusions or comparisons with sibling tools, leaving the usage context inferred.

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