gen_evil

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

No annotations are provided, so the description carries the full burden of disclosure. It transparently states the return value (the evil string and whether it fails to match) and importantly clarifies that a timeout counts as failing, which is a key behavior for understanding the vulnerability.

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 exactly two sentences with no filler. It front-loads the core action, then adds the key return-value detail and timeout semantics, making every word earn its place.

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 tool has 4 parameters, no annotations, and an output schema whose content is unknown. While the description explains the main generation behavior and return status, it omits details about the other three parameters and does not address error cases or engine-specific behavior, leaving the description incomplete for reliable invocation.

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 input schema has 4 parameters with 0% schema description coverage. The description only mentions the pattern placeholder and does not explain the meaning or usage of engine, qlimit, or timeout_ms. With no other source of parameter information, this is a significant gap.

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 begins with a specific verb ('Generate') and identifies the resource ('adversarial string') and the mechanism ('pumps *pattern* and then fails to match, forcing maximal backtracking'). This clearly distinguishes the tool from its sibling gen_benign, which presumably generates benign strings.

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 does not state when to use this tool versus alternatives like gen_benign or redos_bench. It implies use for testing ReDoS vulnerabilities by generating backtracking-inducing strings, but provides no explicit context, prerequisites, or exclusions.

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