adb_ui_find

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

With no annotations provided, the description carries the full burden. It states the tool returns matching elements with coordinates, which is useful. However, it does not mention if the tool has any side effects (e.g., modifying UI state), permissions required, or performance characteristics. More transparency would be beneficial.

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 two sentences with no redundant information. The first sentence captures the core purpose, and the second adds critical context about the return value. Every word serves a purpose.

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 search tool with 4 optional parameters and no output schema, the description is fairly complete. It explains the search criteria and the output (coordinates). However, it could mention what happens if no match is found or if multiple matches exist, but this is not essential for basic usage.

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 schema covers all parameters, but the description adds semantic details: 'case-insensitive' for text and contentDesc, 'partial match' for resourceId and contentDesc. This goes beyond the schema types and provides actionable information for the agent.

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 searches the UI hierarchy for elements matching text, resource-id, or content-description. It specifies the action (search), the resource (UI hierarchy), and the criteria. It distinguishes itself from siblings like adb_ui_dump by focusing on targeted search and return coordinates for precise targeting.

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 implies usage for finding elements to target adb_input actions, but does not explicitly state when not to use this tool or provide alternatives among the many sibling tools. It gives context but lacks exclusion and alternative guidance.

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