ssh_download

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

No annotations provided, so description carries full burden. It discloses overwriting existing local files, read-only remote behavior, local filesystem-only impact, and permission requirements. This fully informs the agent of all behavioral traits.

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?

Four sentences, each with distinct purpose: main action, safety mode, permission requirement, alternative tool. Front-loaded with key action. No wasted words.

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 simple file download tool, the description covers all necessary context: single file, SSH user permissions, overwrite behavior, readonly compatibility. No output schema exists but return value is implied. No gaps for typical usage.

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 covers 100% of parameters with basic descriptions. Description adds value beyond schema by explaining the overwrite behavior and permission context for 'localPath' and 'remotePath', but schema already conveys the primary meaning.

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 it downloads a single remote file via SFTP to a local path, and distinguishes from ssh_sync for directories. The verb 'downloads' combined with resource 'one remote file' and destination 'local destination path' is specific and 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?

Explicitly states when to use (single file) and when not (use ssh_sync for directories). Also mentions it is allowed on readonly/restricted servers and requires read permission, providing clear guidance on preconditions.

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