Waf Bypass

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

The description explicitly states the read-only behavior: 'Read-only: returns text payloads tagged with technique + level, nothing is sent.' and reinforces 'calling this tool does not fire anything at a target.' This goes beyond the annotations by detailing exactly what the tool does and does not do, ensuring users understand its non-intrusive nature.

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 compact and well-organized: it starts with the core purpose, then explains parameters, and ends with behavioral clarification. Each sentence adds value without redundancy, making it easy to scan and understand.

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?

The description gives enough context for typical use: it explains the tool's role in the exploit chain, the input parameters, and the non-sending behavior. It does not detail the output structure (despite an output schema being present) or mention any potential errors or pagination, but for a payload-returning tool this is likely sufficient. The context is adequate but not exhaustive.

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 explains three of the four parameters: vendor (with examples of display names and canonical keys), vuln_class (listing valid values), and level (describing the filter options). However, max_payloads is not mentioned, so its semantics are only inferred from its name and default value in the schema. Overall, most parameters are well explained.

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 tool's purpose: 'Ordered WAF-bypass payloads for (vendor, vuln_class), basic → advanced.' This is specific and unambiguous, and it also explains the ordering logic and the parameters involved.

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 usage context by explaining when this tool is appropriate: 'Payloads are the *data* the exploit chain feeds its validators when a base pass was clean.' It also clarifies that calling this tool does not fire anything at a target, which helps distinguish it from active scanning tools. However, it does not explicitly compare with sibling tools like waf_detect or fingerprint_waf, so guidance is slightly indirect.

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