browser.find_elements

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

Describes return fields (text, href, value, etc.) but does not disclose behavior when no elements match or whether the tool waits for elements. With no annotations, more explicit behavioral details would strengthen transparency.

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 focused sentences: first describes action and output, second provides use case. 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 list-elements tool with no output schema, the description adequately covers the main functionality and output fields. Slightly lacking on edge cases (no match, limit behavior) but sufficient for typical usage.

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%, and the description adds little parameter detail beyond implying selector is a CSS selector. No explanation of session_id or limit, despite limit having default and bounds. The description does not compensate for the lack of parameter descriptions.

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?

Description clearly states the tool finds all elements matching a CSS selector and returns specific attributes. This clearly distinguishes it from siblings like browser.observe or browser.wait_for_selector.

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?

Provides explicit use case ('Useful before clicking or scraping multiple items') but does not mention when not to use or alternatives. Clear context without exclusions.

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