playwright__browser_resize

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

Annotations already indicate the tool is not read-only and is destructive, and the description aligns with that. However, the description adds no extra behavioral context such as side effects on the current page, whether the viewport or outer window is resized, or how this affects subsequent interactions.

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 one short sentence and is front-loaded with the action, which is concise for a simple tool. The '[playwright]' prefix is mildly redundant but does not meaningfully harm clarity.

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?

This is a low-complexity tool with full schema coverage and annotations, so the one-line description covers the core action. It is still incomplete in context: the agent is not told units, whether the change is permanent, or what side effects to expect from the destructive hint.

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%, with both width and height already documented as dimensions of the browser window. The description adds no additional meaning such as units, valid ranges, or constraints, so the parameter semantics rest almost entirely on 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 uses a specific verb ('Resize') and a clear resource ('the browser window'), making the tool's purpose immediately obvious. This action is distinct from sibling tools like navigate, click, or screenshot, even though no sibling comparison is stated.

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 no guidance on when to use this tool or when to prefer an alternative. It doesn't mention responsive testing, viewport sizing, or any exclusion conditions, leaving the agent to infer appropriate use from the tool name alone.

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