browser_resize

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

With no annotations provided, the description must fully convey behavioral traits. It states that resizing affects layout and screenshot size, which is useful. However, it does not disclose other potential side effects (e.g., triggering re-renders, session impact). The information is adequate but minimal.

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 consists of two short, direct sentences. It front-loads the action ('Resize the page viewport') and adds only essential context. No extraneous words.

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 and presence of an output schema, the description covers the core functionality. It could mention error conditions or async behavior, but for a straightforward resize operation, it is sufficiently complete.

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?

The input schema has 3 parameters (width, height, session_id) with 0% description coverage. The description provides an example ('1920x1080') hinting at width/height usage but does not explain valid ranges, units, or the purpose of session_id. This is insufficient compensation for the lack of schema descriptions.

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 uses a specific verb ('Resize') and resource ('page viewport'), and provides an example dimension '1920x1080'. It clearly distinguishes from sibling tools like screenshot or scroll by stating it affects layout and screenshot size.

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?

The description implies usage when changing viewport size but does not provide explicit when-to-use or when-not-to-use guidance, nor does it mention alternative tools. The phrase 'e.g. 1920x1080' offers a typical use case but lacks comparative context.

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