find_element

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

No annotations exist, so the description must fully disclose behavior. It mentions returning 'basic metadata' but does not specify what metadata (e.g., tag, attributes, location). It also does not indicate whether the tool waits for the element or the timeout behavior, leaving significant gaps.

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 very concise with two short sentences, but it sacrifices completeness for brevity. While front-loaded with the verb, the lack of detail makes it minimally adequate.

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 presence of a nested parameter, no output schema, and no annotations, the description is too sparse. It does not explain the return value (beyond 'metadata'), behavior for non-existent elements, or timeouts. The tool's complexity requires more detail.

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 has 0% description coverage, meaning no human-readable explanations for parameters. The description fails to explain how to use the 'selector' object (e.g., 'by' field values, 'value' string) or the 'timeoutMs' parameter. It provides no additional meaning beyond the schema.

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), resource (element), and that it returns basic metadata, which conveys its core function. However, it does not differentiate from sibling tools like 'wait_for_element' or 'get_text', which also locate elements. The phrase 'alias-friendly discovery tool' hints at flexibility but lacks specificity.

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. With many sibling tools for element interaction (click, get_text, wait_for_element), the absence of usage context or exclusions reduces agent decision accuracy.

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