browser_window

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

With no annotations, the description must disclose behavioral traits. It does not warn that 'close' terminates the browser window, mention whether actions are synchronous, or describe side effects. This is a significant omission for a tool capable of closing the window.

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 a single, front-loaded sentence listing the core actions with no fluff. It is appropriately sized for a simple tool, even though it under-specifies behavior.

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 the lack of annotations and output schema, the description is incomplete. It fails to explain parameter conditions, return values, or the destructive nature of 'close', making it insufficient for an agent to invoke the tool correctly in all cases.

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 schema has zero description coverage, and the tool description only repeats the action enum values. It does not explain that width and height are only relevant when action is 'resize', leaving the conditional parameter relationship undocumented.

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 manages the browser window and lists four specific actions (resize, minimize, maximize, close), distinguishing it from sibling tools focused on navigation or tabs. The verb 'manage' is broad, but the enumerated actions ground the purpose.

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 explicit guidance is given on when to use this tool versus alternatives, nor are there exclusions or prerequisites. The intended usage is only implied by the listed actions; for instance, it does not mention that resize may require width and height.

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