browser_resize

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

Annotations already declare destructiveHint=true and readOnlyHint=false, signaling a state-changing operation. The description 'Resize the browser window' is consistent with this but adds no additional behavioral details (e.g., whether it affects screenshots, triggers resize events, or requires a specific browser state). The description does not exceed what annotations already provide.

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, clear sentence with no extraneous words. It is appropriately front-loaded and efficient. However, it could be slightly expanded with minimal context without losing 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?

Given the tool's simplicity (2 parameters, no output schema, annotations present), the description is minimally adequate. It does not explain return values, error conditions, or the effect on the browser state, but the annotations partially compensate. The description is not incomplete to the point of being misleading, but it lacks depth.

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 100%; both 'width' and 'height' have descriptions. The tool description does not add any extra meaning beyond what the schema already conveys. A baseline of 3 is appropriate since the schema sufficiently documents the parameters.

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' clearly states the action (resize) and the resource (browser window). It is specific and distinguishes from sibling tools like 'browser_navigate' or 'browser_take_screenshot' by focusing on window dimensions. However, it does not clarify whether this resizes the viewport or the actual OS 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?

No guidance is provided on when to use this tool versus alternatives (e.g., browser_mouse_move_xy or browser_navigate). There is no mention of prerequisites, context, or exclusions. The description is purely functional with no usage context.

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