close_session

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

Annotations set destructiveHint: true, confirming mutation. The description adds key behavioral details: detach preserves app state, closing terminates chromedriver but keeps Chrome process alive. This goes beyond the annotation.

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?

Three sentences with no redundant information. The most critical information is front-loaded, and each sentence adds unique value: main action, detach details, browser-specific behavior.

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?

The description covers the two main behaviors and their consequences. It lacks explicit mention of return values or post-call state (e.g., need to start a new session), but given the simplicity, this is acceptable.

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?

Schema coverage is 100%, and the description's parameter explanation mirrors the schema. However, the description adds context about auto-detach and session behavior, which marginally enhances understanding 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 clearly states the tool closes the current session or detaches without terminating. It distinguishes between detach and close behaviors and explains specific effects for browser attach sessions. This sets it apart from siblings like start_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?

The description explains when to use detach vs close, mentions auto-detach behavior for noReset sessions, and implies this is the appropriate tool for ending a session. It does not explicitly exclude alternatives but provides sufficient context for typical use.

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