ssh_session_download_content

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

With no annotations, the description must disclose behavior. It only states the output format (base64) but omits details like error handling, file size limits, binary handling, or whether the session must be active. This leaves significant ambiguity.

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 concise with a clear opening sentence and a bullet list of arguments. Every sentence adds value, and the structure is front-loaded. However, the args list is redundant with the schema but is still helpful.

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 and the presence of an output schema, the description covers the basic function. However, it misses essential operational context like session prerequisite, error messages, or binary vs. text handling, which is needed given no annotations.

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 0%, so the description must compensate. It adds minimal context by restating parameter names with brief explanations ('The SSH session ID', 'Path to the file on the remote host'), but does not elaborate on formats, constraints, or examples. Output schema exists but is not described.

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 file content from a remote host via SSH as base64.' It specifies the verb (download), the resource (file content), and the method (SSH as base64). This distinguishes it from siblings like 'ssh_session_command' or 'ssh_session_upload_content'.

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 provide guidance on when to use this tool versus alternatives. It lacks prerequisites (e.g., active session) and context about when download is preferable over other SSH session tools.

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