browser_close

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

The description discloses that the tool kills processes, implying destructiveness, but does not elaborate on consequences (e.g., loss of unsaved data, need for caution). With no annotations, this is insufficient for a destructive 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?

While compact (one sentence), the description is underspecified, omitting critical details about the parameter and usage. Efficiency is not achieved when key information is missing.

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?

Given one unexplained parameter, no output schema, and a destructive operation, the description is starkly incomplete. It fails to explain what the parameter does, what happens after execution, or any warnings.

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 sole parameter 'id' is undefined in the description. Schema coverage is 0%, and the description adds no semantic value about what 'id' represents (e.g., browser instance ID, session).

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 the action (kill all Chrome processes) and target (inside the sandbox), making the purpose clear. However, it does not differentiate from sibling browser tools beyond the name.

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?

No guidance on when to use this tool versus similar tools like browser_navigate or browser_snapshot. The description lacks contextual recommendations or prerequisites.

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