resize_page

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

The description indicates a mutation operation (resizing), but with no annotations, it should detail any side effects, permissions needed, or limitations (e.g., whether units are pixels). The statement is minimal and does not add beyond the obvious.

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 unnecessary words. It is front-loaded with the action and resource, making it efficient and easy to parse.

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 operation, the description together with the schema is mostly complete. However, it does not specify the unit for width and height (likely pixels), which could be ambiguous.

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 clear parameter names and descriptions in the schema itself. The description adds no additional meaning or context beyond the schema, so baseline 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 action ('Resizes') and the resource ('selected page's window'), making it easy to understand what the tool does. However, it does not differentiate from sibling tools like 'set_device_emulation' or 'scroll', which might have related effects.

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 provided on when to use this tool versus alternatives (e.g., set_device_emulation). The description lacks any hints about prerequisites or situations where resizing is appropriate.

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