reverse_shell_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 behavioral disclosure. It only says 'Download' without any details about what happens to the downloaded content (saved to disk, returned as output), whether an active session is required, or potential side effects. This is a significant gap for a tool that likely interacts with a remote system.

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 appropriately short, but it is under-specified rather than concisely informative. It reads more like a title than a description, providing minimal value and lacking structure to guide the agent.

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 simple two-parameter schema and no output schema, the description still fails to convey essential context such as the purpose of each parameter, expected behavior, or return value. It is barely more informative than the tool name itself.

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 does not mention or explain any of the parameters (session_id, remote_file). It provides no meaning beyond what the bare parameter names suggest, failing to compensate for the lack of schema descriptions.

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 states a clear action ('Download') and resource ('via reverse shell'), but the term 'content' is vague and does not specify what is downloaded (file, output, etc.) or the direction. It distinguishes from reverse_shell_upload_content by using 'download' but not from similar tools like ssh_session_download_content or target_download_file.

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?

No guidance is provided on when to use this tool versus alternatives. The phrase 'via reverse shell' implies it is for reverse shell sessions, but there are no explicit context cues, prerequisites, or exclusion statements.

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