bb_payload

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

With no annotations, the description bears full responsibility for behavioral transparency. It only lists capabilities (9 types, 6 encodings) but discloses no side effects, limits, or outputs. For instance, it does not state whether payloads are random, if count affects generation, or if network access is needed.

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 concise sentence in Chinese, front-loading key information (9 types, 6 encodings). No wasted words, but it could still add value without becoming verbose.

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's complexity (multiple payload types and encodings) and absence of annotations, the description is incomplete. It omits parameter details and return value format (output schema exists but unaddressed). Users would lack info to use 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?

The description does not explain what the parameters (count, encode, vuln_type) mean or what values they accept. While it hints at types and encodings, it fails to map 'vuln_type' to payload categories or 'encode' to encoding names. With 0% schema description coverage, the description should compensate but does not.

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 it generates payloads for 9 specific types (XSS, SQLi, SSTI, SSRF, etc.) and supports 6 encoding variants. This distinguishes it from sibling tools like bb_xss or bb_sqli, which are more specific attack tools.

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 alternatives (e.g., bb_xss, bb_sqli). It does not mention prerequisites, context, or conditions where this tool is preferred.

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