start_browser

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

The description lacks disclosure of key behavioral traits. It does not explain side effects (e.g., launching a new browser process), whether multiple sessions are allowed, or what happens on repeated calls. There is no return value description, and no annotations exist to compensate.

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 extremely concise at one sentence, but it sacrifices necessary detail. It is not appropriately sized for the complexity of the tool, as it omits critical usage and behavioral context.

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?

Given the tool's complexity (6 parameters, no output schema, many sibling tools), the description is incomplete. It does not explain what the tool returns, how to configure the browser, or how it fits into a workflow.

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?

With 0% schema description coverage and 6 parameters (including a nested object), the description adds no meaning beyond the schema. It fails to explain the role of parameters like 'browserArgs', 'scriptTimeoutMs', or the 'windowSize' object, leaving the agent to guess.

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 clearly states the action (start) and resource (Selenium browser session). It is specific enough to distinguish from sibling tools, as only this tool initiates a browser session.

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?

No guidance is provided on when to use this tool or when alternatives might be preferred. It does not mention that starting a browser is a prerequisite for other browser actions, nor does it discuss scenarios like reusing a session.

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