Close browser session

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

Beyond the annotations (destructiveHint, idempotentHint), the description adds that closing a session releases all of its pages and isolated browser context, which is a useful behavioral detail. This enriches the agent's understanding without contradicting the provided hints.

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—two short sentences that pack in the action, its effect, and a usage tip. No word is wasted, and the most critical information appears first.

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 single-parameter tool with clear semantics and adequate annotations, the description covers the necessary aspects: what it does, what gets released, and when to use it. The presence of an output schema ensures return values are documented elsewhere, so the description need not address them.

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 does not explain the sessionId parameter in detail; it only refers to an 'explicitly addressed session.' With 0% schema description coverage, more parameter-level guidance would have been helpful, though the tool name and parameter name are intuitive.

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 'close' with a clear resource 'explicitly addressed session' and explains the effect of releasing all pages and isolated browser context. It distinguishes itself from siblings like browser_page_close by focusing on the session-level scope.

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 instruction 'Close each role/account session when its workflow is complete' provides direct guidance on when to call this tool. While it doesn't name specific alternatives, the context makes the use case clear, and the per-session scope is explicit.

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