nex_browser_resize

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

No annotations are provided, so the description carries the full burden. It says nothing about whether the resize persists across navigations, whether it affects screenshots or emulation, or whether the session must already be connected — all relevant for a viewport mutation.

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?

A single short sentence with zero filler, front-loading the action. It is efficient, though its brevity borders on under-specification rather than true conciseness.

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?

With no annotations, no output schema, and four parameters, the description should explain side effects and prerequisites. It leaves the agent without any information on persistence, effect on other browser operations, or failure modes.

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%: pageId and sessionId are documented as defaulting to the active page/session, while width and height have no descriptions but are self-explanatory numeric names with min/max constraints. The description's 'active page' phrasing loosely reinforces the default-target behavior but adds no syntax or unit detail 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?

States a specific verb and resource ('Resize the active page viewport'), which is unambiguous and distinguishable from sibling tools like nex_browser_take_screenshot or nex_browser_scroll that also affect rendering. It does not name any alternative, but the action itself is sharply defined.

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?

There is no guidance on when to resize versus when to capture, scroll, or open a new page, and no prerequisites (e.g., a connected browser session). The agent must infer all usage context 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.