browser_session

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

No annotations are provided, so the description carries the full behavioral burden. It signals that set_default and stop_driver are mutations, but it does not disclose whether the default backend change persists, whether stopping the driver affects active tabs, what status returns, or what permissions or side effects are involved.

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 compact sentence with the core inspect/change framing front-loaded, followed by the three supported operations. There is no redundant or filler wording.

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 two-parameter session-management tool with no annotations and no output schema, the description covers invocation adequately but leaves important gaps. It does not explain the status response, the persistence of set_default, or the consequences of stop_driver.

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 description adds useful meaning beyond the schema by mapping the action enum values to outcomes: show status, switch default backend, and stop driver session. It also links the backend choice to set_default, though it does not explicitly state that backend is only relevant for that action.

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 specific verbs and resource: inspect or change the browser session, with three named operations (status, set_default, stop_driver). This clearly distinguishes it from page-action siblings such as browser_navigate or browser_click, though it does not explicitly contrast it with browser_doctor.

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 three action names imply when each operation is used, but the description gives no explicit guidance on prerequisites, alternatives, or when not to use this tool. It also does not mention browser_doctor as a related diagnostic sibling.

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