ssh_sftp_download

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

No annotations are provided, so the description carries full burden. It mentions the reuse of an existing session, which is key. However, it does not disclose behavior such as whether local files are overwritten, error handling, or permission requirements. This is adequate but could be more detailed.

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 sentence that efficiently conveys the tool's purpose, prerequisite, and mechanism. No unnecessary 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?

Given the tool's simplicity (download file with given paths and session), the description is largely complete. However, it does not mention return values or overwrite behavior. With no output schema, a brief note on success/error would improve 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?

Schema description coverage is 100%: all three parameters (local_path, session_id, remote_path) have descriptions in the input schema. The description adds no additional parameter information beyond the schema. Baseline is 3.

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 'Download a remote file from the board to local over SFTP, reusing an existing SSH session.' It specifies the action (download), source (remote), destination (local), protocol (SFTP), and prerequisite (existing session). It distinguishes from sibling tools like ssh_sftp_upload and ssh_shell_* commands.

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 context by stating 'reusing an existing SSH session,' which indicates an established session is required. However, it does not explicitly state when not to use this tool or reference alternative tools for similar tasks (e.g., uploading via ssh_sftp_upload or shell commands).

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