find_element

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

No annotations are provided, so the description must disclose behavioral traits. It mentions returning information and providing suggestions if not found, but omits details like whether the tool is read-only, what type of information is returned, or any side effects.

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 short, with two sentences. The first sentence is a straightforward statement of function, though it repeats the tool name. The second sentence adds a beneficial behavior (suggestions). No unnecessary fluff.

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?

Despite having an output schema (content unknown) and numerous sibling tools, the description fails to provide crucial context. It does not differentiate from similar tools like find_all_elements, nor does it explain how to specify search criteria or interpret results.

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 two parameters (text and selector) with 0% description coverage. The description does not explain the purpose or usage of these parameters, leaving the agent to infer that they are search criteria.

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 action ('find an element') and the output ('return information about it'). It implies searching by selector or text, which differentiates it from sibling tools like find_buttons or find_inputs that target specific element types.

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 given on when to use this tool versus alternatives like find_all_elements or find_buttons. The description does not mention prerequisites, limitations, or recommended scenarios.

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