Browser wait for selector

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

The annotation readOnlyHint=true already indicates this is a safe read operation. The description adds the behavioral trait of waiting until a state is reached, but does not disclose what happens on timeout, whether it polls, or any side effects. Given the annotation covers the safety profile, this is adequate but not rich in behavioral detail.

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 of 12 words, front-loaded with the main action. Every word earns its place, with no redundant or extraneous information.

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 and 0% parameter description coverage, the description must provide enough context for the agent. It provides minimal information: it waits for a selector state, but does not explain the states (even though they are in an enum), the timeout behavior, or the session requirement. This leaves significant gaps for a tool with four parameters.

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 schema has 0% parameter description coverage, so the description must compensate. However, it provides no explanation of the parameters (state, selector, session_id, timeout_ms) or their meanings. The description mentions 'selector' and 'state' but does not elaborate beyond the parameter names, adding no value to the schema.

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 tool's function: waiting for a selector to reach a requested state in a browser debug session. The verb 'wait' and resource 'selector' are specific, and it distinguishes itself from sibling tools like browser_click or browser_snapshot which perform different actions.

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 usage context (browser debug session, waiting for state) but does not explicitly state when to use this tool over alternatives, nor does it mention any exclusions. A clear purpose provides some implied guidance, but there is no explicit 'when to use' or 'when not to use' information.

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