ui_find_element

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

There are no annotations, so the description should explain side effects, access requirements, or failure modes. It merely says 'control a native app's interface,' which is extremely vague and non-behavioral.

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 only one sentence and there is no wasted prose, but it is under-specified to the point of being useless. It does not convey the tool's actual function, so this is not effective conciseness.

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?

The tool has no annotations, no output schema, and a generic description. For a tool that presumably finds UI elements, the description should at least state that purpose. It is completely inadequate for understanding what the tool does or how to use it.

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 is empty (0 params), and schema coverage is 100% vacuously. With no parameters to explain, the description cannot add parameter semantics, and the baseline of 4 is appropriate.

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 'GUI automation — control a native app's interface' is generic and does not name the specific action 'find element'. It could apply to almost any UI tool, so it fails to distinguish itself from siblings like ui_get_element or ui_read_tree.

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 about when to use this tool versus alternatives. The description gives no context, prerequisites, or exclusions, leaving the agent without any decision support.

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