search_dom_elements

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

No annotations provided; the description suggests a read-only search operation but does not explicitly state whether it mutates state, performance implications, or auth requirements. Adequate but not fully transparent.

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?

Two sentences, each adding distinct value. First sentence states purpose, second mentions return value and subsequent use. No unnecessary words.

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 tool with nested search criteria and no output schema, the description is too brief. It lacks detail on how multiple criteria combine, what the returned 'paths' look like, or pagination behavior. Adequate but not complete given complexity.

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?

Schema coverage is 100% with all parameters described. The description restates that search is by type, content, keywords, or attributes, adding no new semantic value 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 tool searches DOM elements by multiple criteria (type, content, keywords, attributes) and returns matching elements with paths. It is distinct from siblings like analyze_dom_structure or interact_with_element.

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 before navigation, but does not specify when to use vs alternatives (e.g., analyze_dom_structure, interact_with_element). No exclusion or prerequisite mention.

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