Find element

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

With readOnlyHint and openWorldHint annotations already declared, the description adds no additional behavioral context. It does not state whether the tool returns the first matching element or all matches, whether it throws on no match, or how it handles multiple criteria.

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, direct sentence with no unnecessary words, making it concise. It earns its place by stating the core purpose, though it lacks detail.

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 the tool's complexity (12 optional parameters, no output schema) and its close relationship to siblings like waitForElement and assertElement, the description is severely under-specified. It fails to explain behavior, return values, parameters, or usage context, making it difficult for an agent to select and invoke it correctly.

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 has 12 parameters with 0% description coverage, and the description merely says 'by criteria' without explaining any parameter semantics, match types (exact vs contains), or how parameters combine. There is no compensation for the schema's lack of documentation.

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 uses the verb 'Find' and identifies the resource as 'UI elements', which clearly states the core function. However, it does not distinguish from sibling tools like waitForElement or assertElement, which also deal with UI element discovery and verification.

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?

There is no guidance on when to use this tool versus alternatives such as waitForElement or inspect. The description does not mention any conditions, prerequisites, or exclusions for using findElement.

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