Type Text

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

The description only restates the basic action without disclosing behavioral traits beyond the 'destructiveHint' annotation. It does not explain whether text is appended or overwritten, or what side effects (e.g., triggering events) may occur.

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 a single, front-loaded sentence with no wasted words. It conveys the core functionality efficiently.

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 tool has three required parameters and no output schema, the description lacks context about prerequisites (e.g., focusing an element, using a specific device). It does not mention how to prepare the state for this tool or what to expect after typing.

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 input schema has 100% description coverage for all three parameters, so the baseline is 3. The description adds no additional meaning beyond what the schema already provides.

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 'Type text into the focused element', which is a specific verb (type) and resource (focused element). It distinguishes this tool from sibling actions like clicking, tapping, or swiping, as no other sibling tool performs typing.

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 provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites like ensuring an element is focused first, nor does it compare to other input methods such as tapping or pressing buttons.

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