browser_resize

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

The description does not disclose any behavioral traits beyond what the annotations already state (destructiveHint=true, readOnlyHint=false). It adds no context about side effects, state changes, or implications, so the description fails to enrich the agent's understanding beyond the tool's 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?

The description is a single, short sentence, making it concise and front-loaded. However, it is extremely minimal, providing only the action without any elaboration, which slightly reduces usefulness.

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 simplicity of the tool and the presence of annotations (destructiveHint, openWorldHint) and full parameter descriptions in the schema, the description is adequate for basic understanding. However, it omits potential details like units or the distinction between viewport and outer window, leaving minor gaps.

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%, with both width and height having descriptions ('Width of the browser window' and 'Height of the browser window'). The tool description adds no extra parameter semantics, such as units or value ranges, so the baseline of 3 is appropriate.

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 'Resize the browser window' uses a specific verb and resource, clearly indicating the tool's action. It distinguishes itself from sibling tools like browser_navigate or browser_snapshot, though it lacks additional scope detail (e.g., whether it affects the viewport or the entire window).

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?

No guidance is provided on when to use this tool versus alternatives. There is no mention of prerequisites, typical use cases, or exclusions, leaving 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.