Resize Window

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

The description 'Resize the browser window' implies a mutation, which is already indicated by annotations with destructiveHint=true. However, it adds no additional behavioral context such as whether the resize is immediate, whether it affects the viewport, or if there are any constraints (e.g., minimum/maximum dimensions). The description does not enrich the information beyond 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 sentence with no extraneous words. It is concise and to the point, efficiently communicating the tool's purpose. Every word earns its place.

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 tool with complete schema and output schema present, the description is minimally complete. It conveys the core function. It could be improved by mentioning the scope (current window) but the tool name implies page-level scope. Given the low complexity and rich structured metadata, the description is adequate.

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?

Both parameters have descriptions in the input schema (100% coverage). The description 'to specified dimensions' paraphrases the schema but adds no additional meaning or context about the parameters (e.g., units, allowed ranges). Baseline score of 3 is appropriate since schema handles parameter documentation.

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 verb 'resize' and the resource 'browser window'. It distinguishes the tool from sibling tools which cover navigation, clicking, and other actions, but does not specify units (e.g., pixels). The schema provides the parameter descriptions, so the purpose is clear overall.

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 given on when to use this tool versus alternatives. It does not mention prerequisites, side effects, or scenarios like needing to resize for screenshots or responsive testing. The description lacks any usage context or exclusions.

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