browser_resize

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

With no annotations, the description carries the full burden of behavioral disclosure. It usefully clarifies that the resize targets the active page's viewport rather than the whole browser window, but it does not disclose side effects, constraints, or response behavior. This is adequate for a simple operation but not deeply transparent.

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 with no filler, repetition, or schema redundancy. Every word earns its place by clarifying the target and scope of the resize action.

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?

For a simple two-parameter tool with fully documented parameters and no output schema, the description and schema together cover the essential invocation details: what is resized, where it happens, and the two required values. Minor omissions like prerequisites or possible layout side effects do not critically undermine usability.

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 pixel values in the input schema. The description adds no additional parameter-level meaning, so the baseline score of 3 is appropriate.

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 a specific verb ('Resize') and a specific resource ('the active page viewport'), resolving the ambiguity in the tool name. It clearly distinguishes this from navigation, snapshot, and page-management siblings by scoping the action to the viewport of the active page.

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 phrase 'active page' implies that the tool applies to the currently open page, giving a basic usage cue. However, the description does not explicitly state when to use it, note prerequisites such as ensuring a page is loaded, or mention any alternative tools. Usage guidance is only implied, not stated.

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