browser_snapshot_query

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

No annotations provided, so description must carry the burden. It describes a read-only search operation returning excerpts, with no mention of mutations or side effects. Does not explicitly state safety, but the description is consistent with a query tool.

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 well-structured sentences. First sentence conveys action and parameters; 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?

Covers main purpose, search capabilities, and when to use. Lacks details on output format (no output schema), but mentions 'tiny matching excerpts plus paths' which suffices. Adequate for a query tool with 9 parameters.

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 67%; description adds value for text, role, tag, ref, and snapshotId (default behavior). Enhances understanding beyond schema for search criteria. For limit, maxDepth, maxBytes, redact, schema already provides 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 searching a browser_snapshot tree by multiple criteria (text/name/role/ref/tag) and returning excerpts plus paths. It distinguishes from sibling tools like browser_snapshot and browser_snapshot_node.

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 says to use this for drilling into a compact snapshot instead of a full page tree, implying when to choose it over browser_snapshot. Could be clearer about when not to use (e.g., if full node details needed).

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