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 burden of behavioral disclosure. It only states the action without explaining consequences (e.g., whether closing is destructive, if unsaved state is lost, or if it affects the entire application vs. just a session). The parameters hint at session-specific behavior, but the description does not elaborate, leaving the agent without critical knowledge for a mutating operation.

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 ('Close browser'), but it under-specifies rather than being efficiently complete. It is not verbose, but it omits essential details (e.g., parameter semantics, scope). The brevity is not earned; it sacrifices clarity for minimalism.

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?

With no annotations, no output schema, and only a two-word description, the tool is incomplete for an agent to use correctly. It does not clarify what happens when no parameters are provided, how to close all sessions, or the relationship to sibling tools like browser_session. The agent would need to infer too much from the parameter descriptions alone.

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 description coverage is 100% – both 'all' and 'session' have descriptions in the schema. The tool description itself adds no extra meaning about parameters, but since the schema already documents them, the baseline of 3 is appropriate. No additional semantic value is provided 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 states a clear verb ('Close') and resource ('browser'), so the basic purpose is understandable. However, it does not specify the scope (e.g., current session vs. all sessions), and it does not differentiate from sibling tools like browser_session or browser_state. It is minimally clear but lacks precision.

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?

There is no guidance on when to use this tool versus alternatives, nor any mention of prerequisites or context. The description simply says 'Close browser' without explaining whether to use it for closing a specific session, all sessions, or how it relates to other browser_* tools. No exclusions or alternatives are mentioned.

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