ssh_download

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

Annotations are absent, so description carries full burden. It mentions SFTP and recursion behavior, but omits details on permissions, overwrite behavior, error handling, or authentication requirements. Basic behavioral info is present but incomplete.

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?

A single 33-word sentence is concise and front-loaded with the action. Could be structured with bullet points for easier scanning, but remains effective and lacks fluff.

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?

No output schema exists, yet description does not mention return values, success indicators, or error scenarios. Lacks completeness on outcomes and prerequisites (e.g., authentication, storage space). Covers main mechanics but leaves gaps.

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% with descriptions. Tool description adds value by explaining parameter interactions: remotePath supports globs, recursive flag required for directories, and localPath as destination. This goes beyond schema definitions.

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?

Description clearly states 'Download from a remote server over SFTP', identifies the action and protocol. It specifies supported patterns (single file, glob, recursive directory), distinguishing it from sibling tools like ssh_upload.

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 does not explicitly state when to use this tool versus alternatives (e.g., ssh_upload, ssh_exec). No guidance on prerequisites or conditions for use, leaving the agent to infer from context.

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