browser_action

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

The annotations offer no safety hints (all false), so the description must carry the burden. It adds context like 'bounded action' and 'usually a CSS selector,' which hints at behavior. However, it does not disclose side effects, failure modes, or return value expectations, so it falls short of being highly transparent.

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, well-structured sentence that front-loads the action list and includes the key prerequisite (lease_id). It is concise with no superfluous 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?

Even with an output schema present, the tool is complex (6 params, 0% schema coverage). The description omits critical details about parameters like key/value and timeout_ms, prerequisites for specific actions (e.g., wait may not need a selector), and expected outcomes, making it incomplete for reliable invocation.

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 6 parameters with 0% description coverage. The description only mentions lease_id and selector, leaving key, value, timeout_ms, and action semantics (beyond the enum) unexplained. This does not adequately compensate for the lack of schema descriptions.

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 performs one bounded browser action and enumerates the specific action types (click, fill, press, select, wait). This distinguishes it from sibling tools like browser_open and browser_snapshot, which handle navigation and state capture respectively.

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 when an agent has an active lease and needs to interact with a page by specifying 'Requires lease_id and usually a CSS selector.' It provides clear context but does not explicitly mention alternatives or exclusions (e.g., when to prefer browser_snapshot for reading the page).

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