Read window state and geometry

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

readOnlyHint=true is consistent with the description's read-only framing, so no contradiction. Beyond the annotation it discloses the concrete return payload (state enum, position, outer bounds), which is real added value. It omits which window is targeted — presumably the active one given zero parameters — and whether prompts/permissions are involved.

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?

Two sentences, no filler. The returned data is front-loaded and the sibling routing follows immediately after.

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 output schema, the description must carry return-value semantics, and it does name all three returned values and the state enum. A small gap remains around window scoping (which window is measured) and whether coordinates are screen- or viewport-relative.

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 tool takes zero parameters, so the baseline is 4. There is nothing for the description to clarify, though it leaves implicit that the call always operates on the current/active window.

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?

Specific verb (report) plus the exact fields returned: window state with its enum values, screen position, and outer size. It also names the three writer siblings it complements, so an agent can distinguish it from browser_set_window_state / _position / _size without opening a schema.

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 phrase 'readable counterpart of browser_set_window_state / browser_set_window_position / browser_set_window_size' effectively tells the agent to pick this for inspection and those for mutation. It does not, however, address when to prefer it over adjacent readers such as browser_list_windows or browser_screen_info.

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