Get Browser DOM

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

No annotations are supplied, so the description carries the full burden, and it discloses meaningful traits: the return is a *rendered* DOM including dynamically loaded content, and a full-page dump can be tens of thousands of characters (implying cost/size implications). It does not explicitly state the operation is read-only/non-mutating, but 'Get' and the described return value make that unambiguous.

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?

Front-loads the purpose, then a compact list of use cases, then the large-page caveat with the alternative. Every sentence earns its place and the critical routing advice is not buried.

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?

With no output schema, the description explains what is returned (rendered HTML or tag-stripped text) and the size risk, and all six parameters are documented in the schema. An agent has enough to call it correctly and to know when to fall back to browser_snapshot.

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 100%, so every parameter (mode, format, selector, maxLength, sessionId, frameIndex) is already documented in the schema. The description reinforces selector scoping and the smaller text format, but adds no syntax or format detail beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource: 'Get the HTML source code of the current page (or a scoped subtree)', and clarifies it returns the rendered DOM with dynamically loaded content. It also names browser_snapshot as the sibling to use instead for large pages, letting an agent distinguish it without comparing schemas.

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 enumerates when to use it ('find CSS selectors for browser_click/browser_type, understand page structure, check element attributes...') and when not to ('For large pages, prefer browser_snapshot ... or scope with selector'). Both the condition and the alternative are provided.

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