ssh_download

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

With no annotations, the description carries the full burden of behavioral disclosure. It does tell the agent the operation will download and verify a checksum, but it omits important behaviors such as whether the local file is overwritten, what happens on checksum mismatch, and how max_bytes is enforced. The disclosed information is useful but far from complete.

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, front-loaded sentence with no filler. It efficiently communicates the operation and the validation step without 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?

For a tool with four parameters, no annotations, and no output schema, the description is too sparse. It does not explain return values, failure behavior, checksum verification semantics, overwrite policy, connection prerequisites, or how max_bytes limits the download. The agent has enough to guess intent but not enough to invoke the tool safely and predictably.

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 has 0% description coverage, so the description must compensate. It loosely conveys the roles of server, remote_path, and local_path by saying 'from the server to this machine', but it does not document max_bytes or add detail beyond the parameter names. Partial compensation, but a clear gap remains.

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 clear action: download a file from a server to the local machine, with an additional checksum verification step. This distinguishes it from sibling tools like ssh_upload (reverse direction) and ssh_file_read (reading rather than transferring a file).

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 gives the core action but provides no guidance on when to choose this tool over alternatives such as ssh_file_read or ssh_upload, and no prerequisites like an active SSH connection. The agent must infer usage context from the tool name and siblings.

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