web_generate_e2e_harness

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

With no annotations, the description carries the full burden. It implies file generation but does not disclose side effects such as whether outputDir is overwritten, whether network access to target is required, or what happens to existing files. It also omits any return-value or error behavior.

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 single sentence is front-loaded with the core action and lists outputs efficiently. It is dense but every clause contributes to scope, with no obvious filler.

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 six-parameter generation tool that writes files and produces multiple artifacts, the description is missing key operational context: preconditions, whether it writes to disk, overwrite behavior, and what the caller receives. No annotations or output schema exist to fill those gaps.

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 100%, so the schema already documents every parameter including defaults and allowed framework values. The description does not add parameter-level meaning beyond what the schema provides, so the baseline of 3 is appropriate.

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 uses a specific verb-plus-resource construction: extracts routes/forms/API schemas to synthesize Playwright and Cypress E2E suites, mocks, simulator, and runner. This clearly distinguishes it from sibling tools like web_audit_api_catalog or web_synthesize_shadcn.

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?

It states what the tool generates but gives no guidance on when to choose it over alternatives such as web_audit_api_catalog or web_analyze_app_state. There are no exclusions, prerequisites, or contextual triggers for use.

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