playwright__browser_resize

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

The description aligns with annotations: destructiveHint=true indicates state change, which resizing implies. However, it adds no additional behavioral context beyond what the annotations already convey. The description is consistent and sufficient when combined with annotations, but it does not elaborate on side effects like viewport changes or page re-layout.

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 sentence of five words with no wasted words. It is front-loaded and immediately understandable. Every word earns its place.

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 tool's simplicity (two numeric parameters, no output schema), the description is borderline adequate. It does not specify units (pixels), constraints, or how resizing interacts with the page. While the core action is clear, additional context like 'changes the viewport size' or 'affects page layout' would improve completeness without becoming verbose.

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 coverage is 100% with both parameters having descriptions (width and height). The description does not add any meaning beyond the schema; it simply restates the action. Baseline 3 is appropriate as the schema already documents the parameters adequately.

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 'Resize the browser window' is clear, specific, and uses a verb-resource pair. It uniquely identifies the action among sibling tools, as no other tool handles resizing. The purpose is immediately obvious.

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 versus alternatives. It does not mention prerequisites, constraints, or when resizing is appropriate. Sibling tools like 'playwright__browser_navigate' or 'playwright__browser_take_screenshot' are unrelated, but no explicit when-not or context is given.

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