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. 'Resize' implies a mutation, but there is no information about whether this affects the browser window size, persists across navigation, or triggers layout changes. The description is silently under-informative for an agent evaluating side effects.

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 waste. It is front-loaded and immediately states the primary action. However, it is so brief that it sacrifices necessary detail, though this dimension rewards conciseness independently of completeness.

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 four parameters, no annotations, and no output schema, the description is incomplete. It fails to explain measurement units, constraints, side effects, or how pageId/sessionId defaults are resolved. The tool needs at least a few lines covering behavior and parameter specifics.

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 50%: width and height lack descriptions, while pageId and sessionId have some. The description does not clarify units for width/height (pixels vs CSS pixels), default behavior, or how 'active page' interacts with pageId/sessionId. It adds minimal value beyond 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 and resource: 'Resize the active page viewport.' It clearly indicates the action on a page viewport, distinguishing it from navigation, clicking, and other browser operations. However, it lacks a brief note on how this differs from resizing the browser window, which could be ambiguous.

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, nor does it mention any exclusions or prerequisites. There is no mention of alternatives like browser_scroll or browser_tab_new. Agents are left without context for selecting this tool.

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