Close browser

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

The description discloses the core behavior (closing the Chromium window and ending the session) but does not add context about side effects like unsaved data loss or process termination. With no annotations, the description carries the full burden, and it is adequate but not rich in detail.

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 one concise sentence that is front-loaded and contains no unnecessary words. It efficiently conveys the tool's purpose.

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 close operation with no parameters, no output schema, and no annotations, the description is sufficiently complete. It clearly states the action and the object, and there is no missing information required for the agent to invoke the tool correctly.

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 tool has zero parameters, so the description does not need to explain parameter semantics. The baseline for 0 parameters is 4, and the description provides no additional parameter information needed.

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 action ('Close the Chromium window and end the session') with a specific verb and resource. It is distinct from sibling tools, which perform navigation, clicks, typing, screenshots, text extraction, URL retrieval, and evaluation, all of which are different operations.

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 implies the tool is used when the agent needs to close the browser, but it does not explicitly state when to use it versus alternatives or mention any exclusions. Since the sibling tools are all other browser actions, the usage context is clear but not formally guided.

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