adb_find_element

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

The description does not disclose behavioral traits beyond a basic read operation. Without annotations, it fails to mention whether the tool is blocking, how it handles no results, or any side effects, leaving the agent with significant uncertainty.

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 sentence, making it concise. However, it sacrifices critical information for brevity, achieving conciseness at the expense of completeness.

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?

With 8 parameters, no output schema, and no annotations, the description is grossly incomplete. It lacks any details on return values, parameter usage, or usage context, which are essential for a tool of this complexity.

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?

Despite having 8 parameters, the description adds no meaning beyond the raw schema types. With 0% schema description coverage, the description's mention of 'attributes' is too vague, providing no detail on how parameters like text, clickable, or resource_id should be used.

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 tool finds UI elements by attributes using uiautomator, providing a specific verb and resource. While it doesn't explicitly distinguish from siblings like adb_dump_ui_tree, the context implies it's for targeted element search rather than full tree dump.

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 is provided on when to use this tool versus alternatives such as adb_dump_ui_tree or adb_tap. There are no explicit when/when-not statements, nor mention of prerequisites or limitations.

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