reverse_shell_generate_payload

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

No annotations provided, so description carries full burden. It discloses that payloads are generated for manual execution but does not mention network behaviors, authentication needs, or potential risks. As a generation tool, transparency is adequate but could specify that no execution or connection occurs.

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 front-loaded with purpose, then lists parameters in a clear Args block, and ends with return value. Every sentence adds value; no wasted words.

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 4 parameters (1 required), no annotations, and 0% schema coverage, the description covers purpose, parameters, and return. Could mention that generated payloads are ready for copy-paste or that it does not execute them. Output schema exists, so return explanation is sufficient.

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 description compensates well by explaining each parameter: local_ip, local_port with default, payload_type with enumerated examples, encoding with options. This adds significant meaning beyond the schema names.

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 the action ('Generate reverse shell payloads') and the resource ('for manual execution on targets'). It distinguishes from sibling tools like reverse_shell_send_payload by emphasizing manual execution.

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 implies usage for generating payloads to be executed manually, but lacks explicit guidance on when to use this over alternatives like reverse_shell_command or payload_generate. No exclusions or prerequisites are mentioned.

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