Browser Close

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

No annotations are provided, so the description must carry the behavioral burden. It does disclose the key side effect (blanking the page) and the additional effect of close_app (stopping the app), but it leaves unclear whether session state is persisted, what happens to active tabs, or whether there are irreversible consequences.

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 that front-loads the main action and tucks the optional behavior after a semicolon. It is efficient, though it could have used the saved space to define the ambiguous parameters.

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?

This is a session-mutating tool with no annotations gaps are meaningful: device/session semantics are undocumented, the response/output schema is not hinted at, and the consequences for the browser session are only partially disclosed.

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, the description needed to explain device, session, and close_app. It only adds meaning to close_app ('also stops the browser app'); device and session remain undefined, leaving an agent to guess their values and roles.

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 a specific verb-resource pair ('Detach a browser session') and clarifies the destructive scope with 'blanking the page.' It also distinguishes the close_app flag behavior, which helps separate this tool from the many browser_* siblings.

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 gives a clear context for when to call this tool (to detach or close a browser session) and explains the close_app option. However, it does not explicitly compare this tool to sibling alternatives like browser_handoff or browser_open, nor state when not to use it.

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