browser_run_test

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

No annotations provided, so description carries burden. Discloses available Playwright objects but omits side effects (e.g., does it affect VM state?), timeout behavior (though param exists), error handling, or return value. Not enough for safe invocation.

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?

Two concise, front-loaded sentences with no wasted words. Each sentence adds essential context (purpose and available scope).

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?

Despite lack of output schema, description does not explain return value, error propagation, or prerequisites (e.g., VM must be running). Critical gaps for a tool that executes arbitrary code.

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 coverage is low (33% - only script has description). Description adds that script is Playwright body in async context, but fails to explain 'id' (presumably VM ID) or 'timeout_ms' beyond default. Insufficient for a 3-parameter tool with no enums.

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?

Description clearly states verb (run), resource (Playwright test script), and environment (browser inside a VM). Lists available variables, distinguishing it from other browser interaction tools that are more granular.

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?

Implies usage for running custom Playwright scripts, but no explicit when-to-use or when-not-to-use compared to siblings like browser_eval or browser_click_ref. No guidance on prerequisites (e.g., VM must be running).

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