browser_query_selector_all

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says the tool returns metadata and does not explain whether it is read-only, what happens when no elements match, whether it waits for elements, or whether it returns an empty list or throws an error.

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 one concise sentence with no wasted words and the action is front-loaded. It could include more behavioral detail, but as written it is efficient and appropriately sized for a tool with a single parameter.

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?

The tool has one parameter and an output schema, so the basic operation is adequately captured. However, the term 'metadata' is ambiguous, and there is no mention of behavior when the selector matches no elements or whether the page must already be loaded, leaving meaningful gaps.

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% and the only parameter is already described as 'CSS selector'. The description adds no further meaning beyond that, so the baseline of 3 applies because the schema already documents the parameter adequately.

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 uses a specific verb ('Find all elements') and names the resource (elements matching a selector), which clearly conveys the core operation. It distinguishes this from siblings like browser_get_text or browser_get_html, though 'return their metadata' is somewhat vague about what metadata means.

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 offered about when to use this tool versus alternatives such as browser_wait_for_selector, browser_get_attribute, or browser_evaluate. The description implies use for querying multiple elements but does not state when it should or should not be chosen.

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