browser_close

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

With no annotations provided, the description carries the full burden. It discloses the main side effect ('terminate the Chrome process') and the resource-freeing intent. It also explains the default session behavior. However, it does not address edge cases like closing a non-existent session or implications for other sessions, which would be useful for full transparency.

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 concise and well-structured, with a clear first sentence, a usage hint, and an Args section. Every sentence contributes value without redundancy. It is appropriately sized for a simple tool.

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 simple tool with one optional parameter and an output schema present, the description covers the necessary context: what it does, when to use it, and parameter defaults. It lacks minor edge-case behaviors (e.g., error handling for non-existent sessions), but these are not critical for the primary use case. Overall, it is adequately complete.

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 meaning to the sole parameter via the 'Args' section: 'Session to close (default: "default")'. This clarifies the purpose and default value, exceeding the schema which only provides a title and default. Since schema coverage is 0%, this description is essential and fulfills the parameter semantics completely.

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's function: 'Close a browser session and terminate the Chrome process.' It uses a specific verb ('Close') and resource ('browser session'), and includes the additional detail of terminating the Chrome process, which distinguishes it from session-management siblings like browser_list_sessions or browser_open.

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 provides an explicit usage trigger: 'Call this when you're done with a browser session to free resources.' It does not mention alternatives or exclusions, but for a simple close operation this is adequate. The default session behavior is also clarified, which serves as a practical guideline.

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