ssh_download

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

With no annotations, the description must disclose behavioral traits, but it only states the basic action. It does not mention whether existing local files are overwritten, how authentication/credentials are handled, what transfer protocol is used (e.g., SFTP/SCP), or the meaning of the timeout and allow_sensitive parameters. The minimal description fails to convey important behavior.

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 short sentence with no wasted words, but it is under-specified. It lacks necessary context, so the brevity is not appropriately sized for a tool with multiple parameters and no annotations. It is concise but at the expense of completeness.

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 no output schema, no annotations, and 5 parameters, the description should provide more context about return values, error handling, and parameter behavior. It only covers the basic purpose, leaving significant gaps in what the agent needs to use the tool correctly.

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 description coverage is 0%, so the description must compensate. It does not explain any parameter (host, remote_path, local_path, timeout, allow_sensitive) beyond their names. The phrase 'download files' only implies remote_path and local_path, but it does not add semantic meaning to the parameters, especially allow_sensitive and timeout.

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 ('download') and the resource ('files from remote host to local'). It distinguishes itself from sibling tools like ssh_upload (reverse direction) and ssh_download_dir (directory variant), 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?

No guidance is provided on when to use this tool versus alternatives. It does not mention that ssh_download is for single files while ssh_download_dir is for directories, nor any prerequisites like SSH connectivity. The absence of any usage context leaves the agent without decision support.

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