launch_browser

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

With no annotations provided, the description bears the full responsibility for disclosing side effects and operational details. It only states the launch action and does not mention that a persistent browser session is created, that headless mode may be used, or any cleanup expectations.

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 a single sentence that conveys the core action with no unnecessary words. It is front-loaded and efficient, earning a perfect score for conciseness and structure.

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 this simple (one optional parameter, no output schema), the description is minimally sufficient but lacks key context. It does not state what the launch returns, whether the session must be closed via close_browser, or if there are any side effects, making it only adequately complete.

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?

The input schema alone documents the headless parameter with its type, default value, and description, achieving 100% coverage. The tool description adds no extra parameter context, but the schema is sufficiently descriptive, so the baseline score 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 starts with a specific verb 'Launch' and names the resource 'Firefox browser instance' with the technology 'Playwright'. It clearly distinguishes this from sibling tools like close_browser by identifying the exact action and target.

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 provides no guidance on when to use this tool versus alternatives such as close_browser or navigate. It does not mention ordering, prerequisites, or any exclusions, leaving the usage context entirely implicit.

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