reverse_shell_download_content

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

With no annotations, the description carries full burden. It discloses that the output is base64 encoded and mentions two methods (base64, cat). However, it does not address potential side effects (e.g., file not found, permissions, session state changes) or the behavior on error. This is adequate but incomplete.

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 very concise: two sentences plus a bulleted list of parameters. The key purpose is front-loaded in the first sentence, and every sentence adds value. No redundant or verbose wording.

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 presence of an output schema, the description adequately covers purpose, parameters, and return format. However, it does not mention prerequisites (e.g., an active reverse shell session) or potential failure modes. The sibling tools list provides some context, but the description itself could be more self-contained.

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%, so the description must compensate. The Args section explains each parameter's purpose and the valid values for method (base64, cat). This adds meaningful context beyond the schema's titles and types. It could be improved by specifying constraints on session_id or remote_file format.

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 the tool downloads file content from a target via reverse shell and returns it as base64. This clearly specifies the action (download), resource (file content), and method (reverse shell), distinguishing it from siblings like reverse_shell_upload_content or ssh_session_download_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 implicitly indicates use with a reverse shell session, but lacks explicit guidance on when to use this tool versus alternatives such as ssh_session_download_content or target_download_file. No when-not or exclusions are provided, leaving the agent to infer the context from the tool name and sibling list.

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