ssh_download

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

With no annotations present, the description carries full responsibility for disclosing behavior. It only states the basic operation and does not mention side effects such as overwriting existing local files, handling missing remote files, permission issues, or what the return value indicates. This lack of detail leaves significant behavioral uncertainty.

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, concise sentence that conveys the essential purpose without unnecessary words. It is well-structured and immediately informative, achieving maximum conciseness.

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 description, combined with the fully detailed schema, is sufficient for an agent to perform a basic file download. It covers the core operation and all parameters are explained. However, it lacks explicit mention of output/return behavior and edge cases, though these are not critical for a simple download operation. This is slightly above average completeness.

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 descriptions cover all parameters (100% coverage), but the tool description adds no extra meaning beyond what is already in the schema. Since the schema already explains each parameter (e.g., host, remotePath), the description does not enhance understanding. This aligns with the baseline score of 3 for high schema coverage.

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), the object (a file), the direction (from remote to local), and the method (SFTP). This unambiguous purpose differentiates it from siblings like ssh_upload (which does the opposite) and ssh_read_file (which does not save locally).

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 transferring a remote file to the local filesystem, but it does not explicitly state when to choose this over alternatives (e.g., ssh_read_file for viewing content) or provide exclusion criteria. The guidance is clear from context but not explicit, so it falls at the implied level.

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