ssh_session_download_content

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. 'Download via SSH' reveals only that a download operation occurs; it does not state whether an active session is required, what happens on failure, whether the file is written to disk, or any side effects. This is a significant gap for a tool that likely interacts with remote systems.

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 extremely short, but this is under-specification rather than conciseness. It contains only a generic statement that repeats the tool's name and protocol without adding meaningful detail. A concise description should still convey essential usage information.

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 moderate complexity (2 parameters, no output schema, no annotations), the description is far too minimal. It omits critical context such as the source and destination of the download, the need for an existing SSH session, and the expected return format. This leaves an agent unable 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%, and the description adds no information about the parameters 'session_id' and 'remote_path'. The description does not explain how these parameters relate to the download action, making it impossible for an agent to infer correct usage.

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 'Download via SSH' states the verb (download) and resource (SSH), which is clear at a basic level. However, it does not specify what is downloaded (e.g., remote file contents) or how it distinguishes from sibling tools like 'target_download_file' or 'reverse_shell_download_content'. It lacks the precision needed to fully disambiguate the tool's purpose.

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 provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites (e.g., an active SSH session), nor does it clarify whether this tool is for transferring files from a remote system to the local machine. There is no 'when to use' or 'when not to use' context.

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