mobile_type

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

Minimal disclosure beyond the basic action. No details on error behavior if no field is focused, support for special characters, or whether it simulates keyboard input vs. ADB commands. With no annotations, the description carries full burden but provides little.

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?

One concise sentence with clear verb and target, front-loaded and without redundancy.

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 4 parameters and no output schema, the description lacks context on post-typing behavior, error handling, or device prerequisites. Incomplete for a tool with multiple optional options.

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 100%, so baseline is 3. The description adds no new meaning beyond schema; it does not explain optional parameters like serial for multi-device or the effect of clear_first and return_screen.

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') and the target ('currently focused input field on the Android device'), distinguishing it from sibling tools like mobile_button or mobile_gesture.

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 (e.g., adb input, or tools like mobile_gesture). Prerequisites (ensuring an input field is focused) are not mentioned, and exclusions are absent.

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