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 behavioral burden, and it discloses almost nothing: no units (pixels vs CSS px), no note on whether the change persists across navigation or affects screenshots, and no reversibility or permission context. It only implies a state mutation of the viewport.

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 single sentence is front-loaded with the verb and object and contains zero filler. It is efficiently structured, though its brevity borders on under-specification rather than deliberate concision.

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 two-required-parameter mutation tool with no annotations, no output schema, and 0% schema coverage, the definition should at minimum state units and interaction with other browser state. As written, an agent cannot call it confidently without guessing what the numbers mean.

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 0%, so the description must compensate for the two undocumented required parameters, and it does not — width and height are never mentioned, and no unit, range, or format guidance is given. The parameter names are self-evident, which keeps this from being a 1, but no added meaning is supplied.

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 resource (the viewport), so an agent immediately knows this changes the browser viewport dimensions rather than page content. It does not, however, distinguish scope or units, nor reference any related sibling such as browser_emulate_media or browser_take_screenshot, so sibling differentiation is absent.

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 indication of when to reach for this tool, under what preconditions (e.g. after navigation, before a screenshot), or what alternatives exist. The terse statement leaves all usage context to inference.

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