nex_browser_resize

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

With no annotations, the description must disclose side effects, safety, and persistence of the resize operation. It only restates the tool's purpose, offering no additional behavioral context such as whether the page reloads, whether the resize is temporary, or if it affects the session/profile.

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 unnecessary words. It immediately conveys the core action, making it highly efficient.

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?

Given the tool's simplicity, a one-liner might be sufficient, but with no output schema and no annotations, the description should at least hint at return behavior or error conditions. It is minimally adequate for a basic operation but leaves gaps about what the caller receives after invocation.

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 already describes pageId and sessionId (50% coverage), but width and height lack descriptions beyond numeric bounds. The tool description adds no meaning to these parameters, failing to clarify units (e.g., pixels), typical ranges, or how they relate to the viewport.

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 'Resize the active page viewport' clearly identifies the verb (resize) and resource (active page viewport). It is distinct from sibling tools like navigate, scroll, or tab management, leaving no ambiguity about its function.

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, nor any prerequisites such as requiring an active page or a valid viewport. The description only states what it does, not the conditions under which it should be invoked.

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