rush_fuzz

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

With no annotations and low description coverage, the description carries the full burden of disclosing side effects. It mentions --allow-slow as a guard but says nothing about the significant behaviors signaled by parameters such as allow_build, allow_browser, allow_network, allow_download, or artifact writes. It does not state whether it mutates, requires permissions, or runs untrusted code.

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 one compact sentence with no filler, front-loading the two primary use cases and the key guard flag. It is concise and easy to scan, though the dual-mode phrasing creates some ambiguity.

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 10-parameter tool with no annotations, the description is far from complete. It omits prerequisites, side-effect profile, semantics of most parameters, and the relationship between the two modes. An agent could not confidently invoke it correctly based solely on this description.

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%, so the description should compensate. It helps with allow_slow ('under --allow-slow') and weakly implies report_path via 'fuzz report', but it leaves path, options, allow_build, allow_browser, allow_network, allow_download, allow_cache_write, and allow_artifact_write unexplained.

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 names two concrete operations: importing a local fuzz report and executing local fuzz tests under --allow-slow. It adds a usable verb+resource beyond the tool name and gives a sense of scope, though it does not clearly separate the two modes or distinguish itself from siblings such as rush_pbt.

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 gives no guidance on when to choose import mode versus execute mode, nor any alternative tool or exclusion condition. A user must infer from parameter names; the description does not say when to prefer rush_fuzz over related tools.

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