Check test prerequisites

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

With no annotations, the description carries the behavioral burden and does so well: it explicitly declares the operation is read-only and that it will NOT install packages or download browsers — the key safety concern for an agent deciding whether the call is side-effect-free. It omits permission/error behavior, but the critical non-mutation trait is disclosed.

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 safety-relevant "Read-only preflight check" is front-loaded, followed by a tight enumeration of detected artifacts. It is a single dense sentence with no filler, though the long detected-item list reads slightly run-on.

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?

An output schema exists, so return values need not be described. The description adequately conveys what the check covers and that it is non-mutating. The remaining gap is the absence of any routing guidance relative to the sibling check_playwright_config.

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?

There is a single optional parameter whose schema description already covers it (100% coverage), auto-detected if omitted. The description references "a target project" but adds no meaning beyond the schema, so the baseline of 3 applies.

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 opens with a precise verb+resource ("Read-only preflight check for a target project") and enumerates exactly what it detects (Playwright package, CLI, config, browser builds, channels, Allure, artifacts). This is far more specific than the bare title, though it never names the closely related sibling check_playwright_config to draw a boundary.

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?

"Preflight check" implies it runs before test execution, giving implied timing guidance. However, it never states when to prefer this over check_playwright_config or what condition should route an agent here versus elsewhere, so guidance remains implicit rather than explicit.

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