resize_page

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

Annotations provide readOnlyHint=false, indicating mutation. The description confirms this with 'resizes' but adds no extra behavioral context such as side effects, reversibility, or whether it triggers events. With annotations present, the bar is lower, but the description adds minimal value beyond stating the mutation.

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?

Single sentence, 13 words, directly states action and parameters. No waste, front-loaded with key information.

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?

The tool is simple with 2 parameters and no output schema. The description covers the core functionality. Minor gaps: no mention of units (e.g., pixels), possible constraints (min/max size), or interaction with other page states. Adequate for basic use.

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 descriptions 'Page width' and 'Page height'. The description adds slight context by specifying 'selected page's window', but does not elaborate on units, constraints, or format. Baseline 3 is appropriate as schema does most of the work.

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 it resizes the selected page's window to specified dimensions. The verb 'resize' is specific, and the resource is 'selected page's window'. It distinguishes from sibling tools like navigate_page or fill.

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 when to use (when you need to resize a page window) but provides no explicit guidance on when not to use or how it compares to alternatives. No exclusions or sibling references.

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