close-browser

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

With no annotations, the description bears full responsibility for behavioral disclosure. It states the tool closes a browser instance but provides no details on consequences (e.g., resource cleanup), error states for invalid IDs, or whether the operation is reversible. This is a significant gap for a mutation tool.

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 with a single sentence that directly conveys the core function. No unnecessary words or information is included, earning its place efficiently 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 no output schema and no annotations, the description is too sparse. It fails to inform the agent about expected behavior on error, asynchronous nature, or confirmation of success. The tool's simplicity does not excuse the lack of essential operational context.

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% for the required parameter 'contextId', so the baseline is 3. The description does not add useful semantics beyond reiterating the tool's purpose; it neither clarifies the parameter's format nor provides contextual hints, but it meets the minimum standard.

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 action ('Closes') and the resource ('a specific browser instance'), making the tool's purpose unambiguous. It effectively distinguishes itself from sibling tools like 'start-browser' and 'list-browsers' by specifying the closing operation.

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 lacks any guidance on when to use this tool versus alternatives. It does not mention prerequisites, such as ensuring the browser exists, or when to prefer other related tools like 'execute-browser-commands' for more granular control.

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