Resize Window

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

Annotations indicate destructiveHint=true and readOnlyHint=false, already signaling a mutating operation. The description adds no extra context about side effects, such as layout changes or potential reloads, and does not state whether the resize is persistent only for the current session. It fails to disclose any behavioral traits beyond what annotations 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, concise sentence that gets straight to the point without any filler or repetition. It is well-structured and easy to parse, maximizing information density.

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 simple resize tool with a schema covering parameters and output schema present, the description is minimal but adequate. However, it lacks context about when to use the tool and any potential side effects, which limits its completeness for agent decision-making.

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 fully documents both parameters (width and height) with descriptions, giving 100% coverage. The description adds no additional meaning beyond what the schema already states, 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 clearly states the tool's purpose: to resize the browser window to specified dimensions. The verb 'resize' is specific and the resource is the browser window. It differentiates from sibling navigation and automation tools, though it doesn't clarify whether it affects the viewport or the outer 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?

The description provides no guidance on when to use this tool or any alternatives. It does not mention prerequisites, such as needing an active page, or when resizing might be appropriate. Without this context, an agent may misuse or overlook the tool.

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