browser.find_elements

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

The description implies the tool is read-only by stating it returns data, but the annotation has readOnlyHint: false, contradicting the description. No additional behavioral traits are disclosed beyond the schema.

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 concise with two clear segments, but it could be more efficient by also covering parameters. Still, it earns its length.

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?

No output schema exists, and the description only briefly mentions returned fields without structure. It does not address empty results, errors, or session requirements, leaving gaps for an agent.

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 description coverage is 0%, yet the description mentions none of the parameters (session_id, selector, limit). The description adds no meaning to help understand parameter usage.

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 'Find all elements matching a CSS selector and return their text, href, value, bounding box, and visibility', using a specific verb and resource. It distinguishes itself from sibling tools like wait_for_selector and get_html.

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 provides usage context: 'Useful before clicking or scraping multiple items.' However, it does not explicitly state when not to use it or mention alternatives like find_element for single items.

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