Auto-Browser

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

With no annotations provided, the description carries the full burden and successfully discloses key behaviors: it specifies the four possible target states, clarifies the dual outcome paths (returns on success vs raises on timeout), and implies blocking synchronization behavior. It could improve by specifying the exception type raised or noting any polling interval behaviors.

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 consists of two efficient sentences with zero redundancy. It is perfectly front-loaded with the core action ('Wait for a CSS selector...') and immediately qualifies the specific states and outcomes without filler words.

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 4-parameter synchronization tool with no output schema, the description adequately covers the essential behavioral contract (wait conditions and timeout failure). While it omits session_id explanation, the core waiting mechanism and state transitions are sufficiently documented for agent decision-making.

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?

Given 0% schema description coverage, the description partially compensates by mapping 'CSS selector' to the selector parameter and listing the enum values for the state parameter. It implicitly references timeout_ms through 'raises on timeout,' but completely omits the session_id parameter, leaving one required parameter undocumented in natural language.

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 specific action (wait), target resource (CSS selector), and exact scope (states: visible, hidden, attached, detached). It effectively distinguishes this from immediate-query siblings like browser.find_elements by emphasizing the waiting behavior and timeout mechanism.

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 scenarios through 'wait' and 'timeout' concepts, suggesting this is for synchronization when elements aren't immediately available. However, it lacks explicit guidance contrasting this with browser.find_elements or browser.observe, leaving the agent to infer when waiting is preferable over immediate polling.

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