manage_window

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

No annotations are provided, so the description carries the full behavioral disclosure burden. It lists actions and notes that set_rect requires x, y, width, and height, but it does not disclose side effects of maximize/minimize, reversibility, coordinate units, or what state the browser must already be in.

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 compact and front-loaded, with the purpose stated first and the arguments summarized in a short list. Every sentence adds relevant operational information without repeating schema content.

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 has five parameters, no annotations, and no output schema, so the description needs to carry significant weight. It provides the core actions and the required set_rect arguments, but it omits the return shape of get_rect, coordinate semantics, preconditions, and edge cases, making it adequate for basic invocation but not fully complete.

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 description coverage is 0%, so the description must compensate. It usefully explains the action enum values and the dependency of set_rect on x, y, width, and height, but it does not define the meaning, units, or valid ranges of those coordinates, nor how the default get_rect action treats them.

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 opens with 'Get or change the browser window's size, position, or state,' which names a specific action and resource, then enumerates the exact supported actions. This clearly distinguishes the tool from siblings like manage_tabs or manage_cookies, which target different browser resources.

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 the tool: whenever the agent needs to query or modify the browser window's size, position, or state. However, it does not explicitly state when not to use it, mention alternatives, or list prerequisites such as the browser needing to be running.

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