reverse_shell_upload_content

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

With no annotations, the description carries the full burden of behavioral disclosure, but it offers almost nothing. It does not mention whether an active reverse shell is required, whether content overwrites existing files, size limits, encoding, or error behavior. The phrase 'via reverse shell' hints at the mechanism but provides no operational details.

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, front-loaded sentence with no redundant wording. It communicates the core action efficiently. However, it is under-specified, which is penalized in other dimensions rather than here, so the conciseness itself is good.

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 has no annotations, no output schema, and limited schema descriptions, the description is insufficient. It does not explain the prerequisite of an active reverse shell, what remote_path represents, the format of content, or any post-upload behavior. The description adds minimal context beyond the tool name, leaving the agent with significant gaps.

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?

The input schema has zero description coverage for its three parameters (session_id, remote_path, content), and the description does not add any meaning to them. The description simply restates the tool name, leaving the parameters to be inferred from their names alone. This is a complete failure to compensate for the lack of schema documentation.

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 specific action: 'Upload content via reverse shell.' This clearly identifies the verb and resource, and it distinguishes from siblings like ssh_session_upload_content or target_upload_file by specifying the reverse shell mechanism. However, it does not elaborate on what kind of content is expected or the role of the session_id and remote_path parameters.

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 for when to use this tool versus alternatives. It does not mention prerequisites such as an active reverse shell session, nor does it suggest alternative tools like ssh_session_upload_content for different session types. The description leaves the agent without context for tool selection.

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