resize_window

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

No annotations are provided, so the description carries the full burden. It discloses that the action is a resize (a mutation) and that it operates on the current browser window, but it does not mention potential side effects, permission requirements, or behavior on failure. For a simple tool, this is adequate but not comprehensive.

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 two sentences long and front-loads the primary purpose. The second sentence adds a use case and a practical prerequisite. Every word earns its place, with no redundant information.

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?

The tool is simple with three well-described parameters and no output schema. The description covers the purpose, typical use cases, and a necessary prerequisite for obtaining a tab ID. This is complete for an agent to select and invoke the tool correctly without requiring further clarification.

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%, so the baseline is 3. The description does not add any additional meaning beyond the schema; it even repeats the tabId guidance already present in the schema. No extra semantics are provided for width or height.

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 function: 'Resize the current browser window to specified dimensions.' This is a specific verb ('resize') with a clear resource ('browser window') and scope (current window). It distinguishes itself from siblings like navigate or tab_control by focusing on resizing rather than navigation or tab management.

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 provides clear usage context: 'Useful for testing responsive designs or setting up specific screen sizes.' It also gives a conditional prerequisite by advising to use tabs_context first if the user lacks a valid tab ID. However, it does not explicitly state when not to use this tool or mention alternative tools for resizing, so it lacks explicit exclusions.

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