reverse_shell_send_payload

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

With no annotations, the description must disclose behavioral traits, but it only states a generic action. It fails to mention execution behavior, timeout impact, session requirements, or any side effects, leaving the agent completely in the dark.

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 brief but under-specified to the point of uselessness. A single vague sentence does not earn its place because it conveys almost no actionable information; this is incomplete specification, not conciseness.

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 4 parameters, no annotations, no output schema, and no explanation of return values or side effects, the description is fundamentally insufficient for an agent to select and invoke this tool correctly. The context of reverse shell operations and sibling tools is not addressed.

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 meaning to the four parameters (timeout, session_id, wait_seconds, payload_command). It does not explain what session_id references, what payload_command does, or how timeout/wait_seconds affect execution, so the description fails to compensate for the schema gap.

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 ('Send payload via reverse shell') but 'payload' is ambiguous and doesn't specify what kind (command, file, etc.). It vaguely distinguishes from sibling reverse_shell_command by using 'payload' instead of 'command', but the distinction is unclear.

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 sibling reverse shell tools like reverse_shell_command, reverse_shell_upload_content, or reverse_shell_download_content. No exclusions or alternative recommendations are given.

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