Query page elements

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

The description aligns with annotations (readOnlyHint=true, openWorldHint=true) by stating it 'returns' data, implying no mutation. It adds value by specifying that only 'safe attributes' are returned, which is behavioral information beyond the annotations. No contradictions.

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?

A single, well-formed sentence that communicates the essential purpose immediately. No wasted words, front-loaded with the action and outcome. Ideal conciseness for a straightforward tool.

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 description covers the core functionality adequately. With annotations covering read-only and open-world behavior, and an output schema presumably detailing the return structure, the description does not need to elaborate further. It could briefly mention that results are returned as a list or array, but this is a minor gap.

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 high (67%, all parameters have descriptions in schema). The tool description adds no new parameter-specific semantics beyond what the schema provides. It restates the overall purpose but does not elaborate on how 'limit' or 'tab_id' affect behavior.

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 verb 'Return', the resource 'text and safe attributes', and the condition 'matching a CSS selector'. This differentiates browser_query from siblings like browser_snapshot (which returns the full page) and scraper tools (which are for more targeted scraping).

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 does not provide explicit guidance on when to use this tool versus alternatives. It assumes CSS selector knowledge and does not mention when to prefer browser_query over browser_snapshot or scraper_get. Usage context is implied by the tool name but not articulated.

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