browser_resize

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

With no annotations provided, the description alone must disclose behavioral traits such as side effects, persistence, or safety. The description simply says 'Resize the page viewport,' which only restates the action itself. It does not mention whether the page reloads, whether the resize is temporary, or whether it affects the layout in unexpected ways. The agent is left without information about the tool's impact beyond the obvious resize.

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, concise sentence with no filler words. It is appropriately front-loaded—the entire sentence is the core message. However, it is arguably too terse, lacking important details that would make it more useful, but as far as conciseness and structure go, it earns its place without redundancy.

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 low complexity of the tool, the description is disproportionately minimal. It fails to provide essential context such as units for width/height, what happens to the current page, or whether the viewport resize is a temporary state. With no annotations and no output schema, the description should carry more explanatory weight, but it provides only a bare restatement of the tool's purpose.

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 defines width and height as numbers but provides no units, constraints, or description. The tool description does not mention the parameters at all, so it fails to clarify units (e.g., pixels) or any relationship between width and height. Schema description coverage is 0%, and the description does not compensate for this gap.

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 page viewport.' It uses a specific verb ('resize') and a specific resource ('page viewport'), which distinguishes it from sibling tools like browser_navigate, browser_screenshot, etc. There is no ambiguity about what operation this tool performs.

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 any prerequisites, use cases, or exclusions. For example, there is no indication whether resizing is typically done before a screenshot or snapshot, or if there are constraints on width/height values. This lack of context leaves the agent to infer usage solely from the tool name.

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