resize

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

No annotations are provided, so the description carries the full behavioral burden. It omits units (likely pixels), minimum/maximum dimensions, whether it affects only the current tab, whether it triggers reflow or resize events, and whether the change persists.

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 front-loaded sentence with no filler. It is concise, though arguably too terse for a three-parameter viewport operation.

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?

With no annotations, no output schema, and incomplete parameter documentation, the description should explain units, constraints, tab behavior, and expected effect. It leaves all of that unspecified, so an agent cannot reliably invoke the tool without inspecting the schema or guessing.

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 only 33%: only the tab parameter is documented as defaulting to the current tab. Width and height have no descriptions, and the tool description adds no unit, range, or constraint semantics beyond the word 'resize', so it fails to compensate for the missing schema detail.

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?

States a specific verb (resize) and resource (viewport), reinforced by the width/height parameters. It is clear what the tool does, but it does not explicitly distinguish itself from the maximize/minimize siblings.

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?

Provides no guidance on when to use resize instead of maximize or minimize, nor any prerequisites such as needing an active tab. Usage is only implied by the tool name and action verb.

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