browser_type

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

With no annotations, the description carries the burden: it usefully discloses that text is replaced by default unless append is true and that submit presses Enter. It does not say whether the element is scrolled into view, whether focus is required, what happens if ref is stale, or what the tool returns on failure.

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?

A single tightly-packed sentence with a parenthetical handles the append default up front and finishes with the submit behavior. Nothing is wasted, though the dual typing/select mode is slightly buried mid-sentence.

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 mutation tool with no annotations and no output schema, the description covers the core semantics but leaves out error/failure behavior and post-action state, which an agent would want before calling it in a live browser session.

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 coverage is already 100%, so the baseline is 3, but the description adds real meaning: ref is specifically the number produced by browser_read, text is overloaded to mean either typed text or the option label for a select, and append/submit are framed as behavior toggles rather than bare flags.

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?

States a concrete verb (type) and resource (text field / select), and clarifies that the target is identified by the number returned from browser_read. It distinguishes two modes (typing into a field vs. picking a select option), but never mentions how it differs from the sibling type_text or browser_click.

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 the usage context by tying ref to browser_read, and explains when append applies. However, it gives no explicit 'use this instead of type_text/browser_click' routing guidance, so an agent must infer which tool to pick for browser vs. non-browser input.

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