browser_session

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

Annotations already indicate destructiveHint=true and readOnlyHint=false, so the description does not need to restate safety. It adds that start requires a specific path, but does not elaborate on effects like session isolation, what happens on stop, or output format, providing only minimal addition over annotations.

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 front-loads the actions and includes a critical constraint. It is efficient with no wasted words, though it could benefit from a clearer separation of operations and outcomes without losing conciseness.

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 has multiple operations and no output schema, the description is too brief. It does not explain what each operation returns (e.g., list yields session IDs, status gives session state), nor does it cover edge cases like what happens when no session is active. An agent would need additional inference for full understanding.

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 75% schema description coverage, the schema already documents most parameters. The description adds one behavioural note about launchJson being required for start, which is useful but not extensive. It does not clarify session or configuration semantics beyond the schema.

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 lists the core operations (start, select, inspect, list, stop) on 'isolated project browsers', clearly indicating the tool manages browser session lifecycles. It distinguishes well from siblings like browser_observe and browser_act, which handle interaction within sessions.

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 mentions that 'Start requires an AL launch.json path', providing a specific prerequisite. However, it offers no guidance on when to use this tool versus alternatives (e.g., browser_observe for observing elements) or which operation to choose in different scenarios.

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