browser_resize

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states 'resize browser window size' with no information about side effects (e.g., affecting subsequent screenshots or responsive layout), prerequisites (e.g., browser must be open), or error handling. The description adds no behavioral context beyond the operation itself.

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, concise sentence with no redundant or unnecessary information. It is appropriately sized for a straightforward resize operation, front-loaded with the essential meaning.

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 tool with no annotations and no output schema, the description should provide more context about how resizing affects the browser session, when to use it, and any limitations. It currently only states the action, leaving the agent without enough information to fully understand the tool's role in the browser workflow. The schema descriptions help for parameters but not for the tool's broader context.

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 each parameter having a Chinese description (width, height, and a detailed explanation of _agent_id). The description itself does not add any additional meaning beyond what the schema already provides, so it meets the baseline but does not exceed it.

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 (resize) and resource (browser window size). It distinguishes from sibling browser tools like navigate, click, and type, which perform different actions. However, it is essentially a restatement of the tool name with minimal additional detail, so it lacks the specificity of higher-scoring descriptions.

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?

There is no guidance on when to use this tool versus alternatives. The description does not mention any context such as resizing before taking a screenshot or how it interacts with other browser tools. No exclusions or alternative tool recommendations are provided.

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