type_text

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

Discloses the default clearing behavior, which is important for understanding side effects. However, it does not explain what happens if the element is not found, whether it waits for the element, or how typing is simulated (e.g., key events vs. value setting). With no annotations, the burden is higher.

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?

Single sentence, no fluff. Front-loaded with the core action and target, then the key behavioral note. Every word earns its place.

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 simple type action, the description covers the essential: what to type and where. But it omits return value, error handling, and whether the element is focused. With no output schema and 3 parameters, more context would be helpful (e.g., 'returns success or throws error if element not found').

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 must define parameters. It indirectly covers 'selector' and 'text' through the phrase 'by selector' and 'type text', and adds meaning for 'clearFirst' by stating the default. However, it does not explicitly describe the 'text' parameter or explain what 'selector' means (e.g., CSS selector).

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 action 'type text', the target resource 'input/textarea', and the method 'by selector'. It also specifies a key behavioral detail: 'clears it first by default'. This is distinct from sibling tools like 'click' or 'press_key'.

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?

No guidance on when to use this tool versus alternatives like 'press_key' or 'eval_js'. It does not mention prerequisites, limitations, or conditions that would help an agent choose correctly.

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