type_text

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

No annotations are present, so the description carries the full burden. It discloses that the tool clears the field, types the text, uses a default 7-second timeout when timeout is 0 or None, and raises an exception if the element isn't found within the timeout. These are key behavioral traits beyond what the schema shows.

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?

Three short sentences with no filler. The primary action is front-loaded, followed by the default timeout behavior and the exception condition. Every sentence adds value.

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?

The description covers the core action, timeout semantics, and failure behavior. Since an output schema exists, return value details are not needed. It does not mention selector format or element visibility requirements, but these are common and not critical for correct 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 0% description coverage, so the description must compensate. It adds meaningful semantics for the timeout parameter, including the 7-second default and failure behavior. Selector and text are not described, but their purpose is fairly self-evident from their names and from the action description.

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 a specific action: clear a field and type text into it. This distinguishes it from related siblings like send_keys (which types without clearing), clear_input (which only clears), and set_value (which may not clear-and-type in the same way).

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 clear-and-type phrasing provides strong contextual guidance: use this tool when you want to replace the current contents of a field. It does not explicitly name alternatives or when-not-to-use, but the behavior is distinct enough that an agent can infer the appropriate usage.

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