payload_generate

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It merely says 'Generate payload.' with no information about side effects (e.g., file creation), output format, or execution environment. This is severely lacking for a tool that likely generates binary executable files.

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 extremely short, but this is under-specification rather than conciseness. A single phrase without supporting detail wastes the opportunity to provide essential context. It is akin to the 'Process' example in the calibration guide.

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?

This tool has 10 parameters, no output schema, no annotations, and a very short description. The description leaves nearly all contextual information unstated (e.g., output path, supported payload types, relation to host/pivot tools). It is far from adequate for an agent to select and invoke the tool correctly.

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?

With 10 parameters and 0% schema description coverage, the description provides no additional meaning for any parameter. The schema includes defaults (e.g., payload 'windows/meterpreter/reverse_tcp', lport 4444), but the description itself adds nothing to help an agent understand the function of encoder, bad_chars, template_name, or iterations.

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 'Generate payload.' is essentially a tautology of the tool name (payload_generate) and provides no specificity about the kind of payload, target platform, or purpose. It does not distinguish this tool from siblings like reverse_shell_generate_payload or payload_one_liner.

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?

There is no guidance on when to use this tool versus alternatives, no mention of the required lhost parameter, and no typical workflow or prerequisites. The description offers zero context for usage decisions.

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