browser_type

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

Annotations only declare readOnlyHint=false and openWorldHint=true; the description adds real behavioral context by disclosing that keystrokes are emitted individually as genuine key events (which can trigger autocomplete side effects) and that submit fires Enter afterwards. It does not cover failure behavior when the element is missing, which keeps it below 5.

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 front-loaded sentence with the key-events mechanism stated first and the Enter behavior tacked on compactly; no filler or redundant phrasing.

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 6-parameter, fully documented schema with no output schema, the description gives enough to call it correctly, including the focused-element fallback. Minor gaps remain on how refs are resolved and what happens if the ref is stale.

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 description coverage is 100%, so ref, text, selector, value, submit and snapshot are all documented already. The description only restates the submit semantics and notes the 'focused element' fallback when no ref is supplied, adding little beyond the schema — baseline 3.

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 specific verb (type) and resource (element or focused element) plus the mechanism (key by key, real key events). The phrase 'as real key events autocompletes see' effectively distinguishes it from the direct-value sibling browser_fill, though it never names that sibling explicitly.

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?

Implies the usage context (autocomplete widgets that need genuine key events) and explains the submit option, but gives no explicit when-to-use/when-not guidance and does not route the agent to browser_fill or browser_press_key when those would be more appropriate.

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