rush_e2e

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only mentions the --allow-browser gate. It does not state whether the test run can modify the workspace, write caches/artifacts, or make network calls, nor what happens if the required flag is omitted.

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 description is terse and front-loaded with the main purpose, which is good. However, given the nine-parameter input schema, it is under-specified rather than appropriately sized; brevity comes at the cost of necessary semantic content.

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 tool with nine input parameters, two required, and no annotations, this description is far from complete. It covers one condition and does not explain required inputs, the remaining permission flags, or how the tool relates to sibling test tools; the existence of an output schema only slightly reduces the need for return-value explanation.

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 needed to compensate, but it only explains one parameter (allow_browser via '--allow-browser'). It provides no meaning for the required 'path' and 'options' parameters—'options' has no type in the schema—or the other six allow_* flags.

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 ('Run') and a specific resource ('configured E2E tests'), so an agent immediately knows what the tool is for. The qualifier 'only with --allow-browser' also signals this is a browser-gated E2E runner, though it never explicitly names a sibling tool such as rush_test for contrast.

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 an explicit invocation condition: use this tool for configured E2E tests and only when --allow-browser is available/enabled. It does not list exclusions or alternatives like 'for unit tests use rush_test', so it stops short of full routing guidance.

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