Find input field by label and type into it

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

Annotations indicate it modifies state (readOnlyHint=false) and is not idempotent. Description adds heuristic steps and action sequence (locate, tap focus, type). Missing detail on whether existing text is cleared or appended.

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?

Two sentences, front-loaded with purpose and heuristic summary. Every sentence adds value with no 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?

Describes heuristic but return value is vague ('matched field summary'). No output schema, so more detail on return structure would improve completeness.

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%, baseline 3. Description adds heuristic matching details for 'label' parameter, explaining it can match contentDescription, hint, or sibling label, which aids understanding beyond schema.

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?

Title and description clearly state the action: find input field by label and type into it. Description details heuristic steps, distinguishing it from siblings like devilge_input_text (which types without finding) and devilge_tap_text (which taps without 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?

Usage context is implied by the name and description, but no explicit when-to-use or when-not-to-use is given. No mention of alternatives like devilge_tap_resource_id or when the heuristic might fail.

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