type_text

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

With no annotations, the description must carry the behavioral burden. It discloses the mechanism (CDP Input.insertText) and the active-tab default. However, it does not explain what element receives the text, whether key events are fired, or how focus is handled, leaving meaningful behavioral ambiguity.

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 compact and front-loaded with a concrete example, which makes it easy to scan. It wastes no words, though the mixed Chinese/English formatting and missing clear parameters explanations slightly reduce readability.

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?

Given the low complexity (2 params, no output schema), the description is somewhat adequate, but the large sibling set includes overlapping tools like fill_input and press_key. The description fails to explain where this low-level CDP primitive fits, what happens with no focused element, and let alone return values or side effects.

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 0%, so the description is responsible for explaining the parameters. It explains that 'tab' targets a label and defaults to the active tab if omitted, and the example implies 'text' is the string to type. However, it doesn't specify the type/format for tab, how to identify the tab, or any constraints on text.

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 indicates the tool performs text insertion by naming 'CDP Input.insertText' and showing an example call 'type_text("hello")'. The verb 'type_text' and the CDP reference distinguish it from higher-level tools like fill_input, though it doesn't explicitly compare with siblings.

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 mentions that omitting the 'tab' parameter types into the current active tab, giving minimal context. However, it provides no guidance on when to prefer type_text over sibling tools such as fill_input, press_key, or click, and no exclusions or alternatives are named.

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