browser_resize

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

Annotations declare readOnlyHint=false, destructiveHint=true and openWorldHint=true, but the description adds nothing about what 'destructive' means here (changing viewport state, possible reflow), whether the window must exist, or what the resulting size units are. It simply repeats the annotation title.

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, front-loaded sentence with zero waste and no burying of key information, though its brevity reflects under-specification rather than disciplined editing.

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 three parameters, a session-isolation model, and destructive/openWorld annotations but no output schema, the description should mention units, required preconditions (open session), and the visible effect of the resize. None of that is present.

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 100%, including width, height and the session parameter, so the schema carries the semantics and baseline 3 applies. The description adds no units (pixels vs CSS px), no min/max bounds, and no explanation of how width/height interact with the session parameter.

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 concrete verb and resource ('Resize the browser window'), so an agent knows the general action, but it is essentially a restatement of the name and title with no differentiation from siblings such as browser_emulate_media or browser_take_screenshot (where viewport size matters).

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 use this versus alternatives, no mention that a browser/session must already be open, and no indication of whether resizing affects screenshots or snapshots. The agent must infer all usage context.

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