pentest_exploit_payload_generate

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

With no annotations present, the description carries the full disclosure burden and does meaningful work: it reveals a gating flag, a required confirmation phrase, a mandatory human-in-the-loop step, and where output lands (the evidence directory). It still omits whether an existing file is overwritten, what error surfaces when prerequisites fail, and whether the payload is ever executed — gaps that matter for a security-sensitive tool.

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?

Three short lines, front-loaded with the action and followed immediately by the safety preconditions. Every sentence earns its place, though the trailing standalone confirmation line could be folded in without loss.

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?

For a 7-parameter, zero-coverage mutation tool with no annotations and no output schema, the description covers only the authorization gating. An agent still cannot tell what values to supply for most parameters or what the tool returns, so it is not complete enough to invoke confidently without opening external documentation.

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% across 7 parameters, so the description must compensate and largely does not. Only confirm_phrase gains meaning (it must match the engagement_id); lhost, lport, payload, encoder, iterations, and output_format are left entirely undocumented, including expected formats and valid msfvenom values.

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?

States a specific verb and resource: generate a payload with msfvenom, written into the engagement evidence directory. That scope distinguishes it reasonably well from siblings like pentest_exploit_msf_run and pentest_exploit_search, though the description never names those alternatives explicitly.

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?

Gives concrete preconditions for use: rules.allow_payload_execution must be true and confirm_phrase must equal the engagement_id, plus an instruction to obtain explicit human confirmation first. It does not point to alternatives such as msf_check or msf_run when the conditions are not met, which keeps it short of a 5.

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