find_elements

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

The description explains the tool's behavior (search, return matching elements) and parameter details, but does not mention idempotence, performance implications, or lack of side effects. Without annotations, more transparency is needed.

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?

Well-structured with a concise intro paragraph followed by parameter descriptions. Some redundancy (e.g., 'Args' section could be more list-like), but overall efficient and front-loaded.

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?

Covers prerequisite, all parameters with details and defaults, and briefly describes return values. Despite no output schema, the description is sufficient for a tool with 6 parameters and moderate 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?

With 0% schema coverage, the description fully compensates by explaining all 6 parameters: session_id required, query (case-insensitive substring match), element_types filter, visible_only default true, frame_context, max_results default 25. Adds meaning beyond types.

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's purpose: 'Search for specific interactive elements on the current page' and lists returned data (selectors, text, attributes). It is specific and distinct from siblings like scout_page_tool and inspect_element_tool.

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?

Explicitly instructs to 'Call scout_page_tool first to cache the page structure, then use this tool to find specific elements', providing clear prerequisite context. However, it lacks explicit 'when not to use' or alternative tools.

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